analyze_page_seo

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

No annotations are provided, so the description carries the burden of transparency. It discloses the tool is 'instant' and lists the output categories, but does not mention any operational details like error handling, rendering requirements, or potential side effects. For a read-only audit, this is adequate but not rich.

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 two sentences, front-loaded with the action, and contains no filler. It efficiently conveys purpose and key output details.

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?

With one parameter and no output schema, the description covers the essential return values and purpose. It is reasonably complete for a low-complexity tool, though it could briefly mention what 'technical issues' entails or any limitations (e.g., requires accessible public URL).

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?

Schema coverage is 100% for the single parameter 'url' with a clear description. The tool description adds no extra meaning beyond the schema, which already fully documents the parameter, so the baseline score of 3 applies.

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 tool 'Performs an instant on-page SEO audit of a URL,' using a specific verb and resource. It lists the returned elements (title, meta, headings, etc.), making it distinct from sibling tools like get_page_lighthouse or analyze_content_sentiment.

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?

The description implies usage context through 'on-page SEO audit' but provides no explicit when-to-use or alternatives. It doesn't compare against sibling tools like get_page_lighthouse or get_search_intent, leaving the agent to infer when this tool is appropriate.

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