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

There are no annotations, so the description carries full responsibility for disclosing behavior. It mentions what areas are checked but does not explain side effects, permissions, network access, return format, or whether this is a read-only operation. The agent is left guessing about the tool's runtime 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 very short and front-loaded, but it is under-specified rather than appropriately concise. It is a fragment listing three items without a complete sentence, which limits clarity. It does not waste words, but it also fails to provide enough structure to be genuinely concise.

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 no annotations, no output schema, and a low-complexity tool, the description is incomplete. It does not describe what the tool returns, how results are presented, or the exact scope of 'passage citability'. The agent cannot confidently invoke this tool based on the given information.

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 provides minimal information (a required url with format uri). The description adds context that the url is the target for AI search readiness checks, but it does not explicitly describe the parameter or its expected values. Some meaning is added beyond the schema, but it is minimal.

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 the tool covers 'AI search readiness' and lists specific check areas (crawler access, llms.txt, passage citability), but it lacks an explicit verb and does not differentiate itself from sibling SEO check tools. It is not a tautology, but the purpose is only implied by the tool name.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or contrast with sibling tools like seo_check_content or seo_check_meta, leaving the agent without context for appropriate selection.

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