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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds context: free, no API key needed, outputs specific scores and an AI Identity Card, and performs 77+ checks across 12 categories. It does not contradict annotations and provides extra behavioral details beyond what annotations offer.

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 paragraph that front-loads the main purpose, then details outputs, exclusions, and alternatives. Every sentence contributes value, though it could be slightly more concise by removing the '77+ checks' detail, which is additional but not critical.

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 fully explains the return values: three scores with ranges, AI Identity Card components, and top 5 issues. It also mentions the scope (77+ checks, 12 categories) and what is excluded. With annotations providing safety context, the description is complete for an agent to understand the tool's purpose and output.

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% with both url and pages described. The description reiterates that pages controls the number of pages to scan but adds no further semantic meaning beyond the schema. The free and no-API-key information is contextual but not parameter-specific.

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 a 'Quick AI visibility scan' and returns specific scores (AEO, GEO, Agent Readiness) and an AI Identity Card. It explicitly distinguishes itself from sibling tools by stating what it does NOT return and recommending alternatives like audit_site, fix_site, and compare_sites.

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?

Explicitly states when to use ('Quick AI visibility scan'), that it's free and requires no API key, and provides clear exclusions: 'Does NOT return per-check details or fix code — use audit_site for full breakdown, fix_site for generated fixes, compare_sites to benchmark against a competitor.'

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