Page or section
docs/toolhive/integrations/vault.mdxdocs/toolhive/integrations/aws-sts.mdxdocs/toolhive/integrations/ingress-ngrok.mdx
What could be better?
The front matter descriptions on these pages start with filler openers the description guidelines say to avoid: vault and aws-sts start with "Learn how to," and ingress-ngrok with "A guide to." The first ~70 characters of a description double as the DocCard preview, so the filler crowds out the useful summary.
Proposal
Rewrite the three descriptions to lead with the action or topic, keeping the first 70 characters as a standalone summary (80-150 characters total). Example shape for vault: "Securely manage MCP server secrets using HashiCorp Vault with the ToolHive Kubernetes Operator." No other pages need this treatment; the common "How to ..." opener elsewhere leads with the action and is fine.
Page or section
docs/toolhive/integrations/vault.mdxdocs/toolhive/integrations/aws-sts.mdxdocs/toolhive/integrations/ingress-ngrok.mdxWhat could be better?
The front matter descriptions on these pages start with filler openers the description guidelines say to avoid:
vaultandaws-stsstart with "Learn how to," andingress-ngrokwith "A guide to." The first ~70 characters of a description double as the DocCard preview, so the filler crowds out the useful summary.Proposal
Rewrite the three descriptions to lead with the action or topic, keeping the first 70 characters as a standalone summary (80-150 characters total). Example shape for vault: "Securely manage MCP server secrets using HashiCorp Vault with the ToolHive Kubernetes Operator." No other pages need this treatment; the common "How to ..." opener elsewhere leads with the action and is fine.