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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the agent knows this is a safe, repeatable read operation. The description reinforces non-mutation with 'Does not save anything' and mentions the return shape, but it adds little new behavioral context such as authentication needs, rate limits, or URL-fetching behavior.

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 three short sentences with no wasted wording. It front-loads the core purpose, then states the return values, then notes that nothing is saved.

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?

Given the lack of an output schema, the description usefully explains that the tool returns a 0-100 score, a traffic light, and per-check results. Annotations cover the safety profile, and the accepted input formats are stated, though the relationships among the six optional parameters could be clearer.

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 description coverage is 50%, and the description adds meaning by indicating that the analyzer accepts Markdown, HTML, or a page URL, which maps to the markdown, html, and url parameters. It does not clarify that these inputs are likely alternatives, nor does it explain the roles of lang, keyphrase, or the optional site parameter beyond the schema's own notes.

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 states a specific action and resource: it runs an SEO, readability and GEO analyzer on Markdown, HTML or a page URL. This is clear enough for an agent to understand the core purpose, but it does not explicitly differentiate this tool from siblings like get_url_audit or compare_with_top_results.

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 by naming the accepted input types (Markdown, HTML, or a page URL), which gives context for when the tool applies. However, it provides no explicit guidance on when to choose this tool over alternatives such as get_url_audit, crawl_site, or compare_with_top_results.

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