audit-seo

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'analyze', implying a read operation, but fails to mention whether it fetches the page, any prerequisites, rate limits, or what constitutes 'SEO metadata and structure'. This lack of detail reduces transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, a single sentence that front-loads the action and target. However, it is under-specified, lacking definitions for ambiguous terms like 'SEO metadata' and 'structure', which diminishes its overall effectiveness despite its brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal and incomplete. There is no output schema or annotations to provide additional context, and the vague phrasing does not clarify what the analysis entails or what results the agent can expect. Given the existence of closely related sibling tools, this description is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already fully describes the only parameter (url) with a clear definition, and the description adds minimal extra meaning by reiterating that it's the webpage to analyze. Given high schema coverage (100%), the baseline is 3, and the description doesn't significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (analyze) and the resource (SEO metadata and structure on a webpage), making the core purpose understandable. However, it does not distinguish this tool from overlapping siblings like check-page-metadata or evaluate-page-structure, so it lacks differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus the many similar marketing/SEO analysis tools. The description neither mentions alternatives nor specifies the context in which this tool is preferred, leaving the agent without clear selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.