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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Check' implies a read-only inspection, but it does not state what the tool returns, how it handles errors, or any other behavioral traits. It lacks information on output format, auth requirements, or failure modes.

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 a single, concise sentence with no filler, leading with the verb and listing concrete items. It is efficient and front-loaded, though slightly terse, earning a high but not perfect score.

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 only one parameter and no output schema, the description should explain the expected return value or usage context, but it only lists the checks. It also lacks any usage guidance or differentiation from sibling tools, making it incomplete for an agent selecting among 14 SEO tools.

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 input schema has one parameter 'url' with zero description coverage (0%), and the description does not explicitly mention the URL parameter or explain how it is used. While the context implies the URL is the target of the check, the description fails to compensate for the schema's lack of semantic detail, adding minimal value beyond the schema.

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 uses a specific verb 'Check' and enumerates the exact elements inspected (title, meta description, OG tags, canonical, robots directives), making the purpose clear. However, it does not distinguish from sibling tools like seo_check_content or seo_check_schema, so it lacks sibling 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?

There is no guidance on when to use this tool versus alternatives or siblings. No context, prerequisites, or exclusions are mentioned, 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.