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

Annotations declare readOnlyHint=true and openWorldHint=true, so the agent already knows this is a safe read operation that accesses the open web. The description adds what specifically gets scanned (crawler rules, llms.txt, schema.org data, etc.), which is useful behavioral context. It does not disclose rate limits, authentication needs, or runtime behavior, but with annotations covering the safety profile, a 3 is appropriate.

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, front-loaded sentence that states the score, its range, and what it evaluates, ending with a clarifying exclusion. It is dense but every clause serves the purpose of explaining what the score covers. No wasted words.

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?

For a simple read-only tool with one parameter and no output schema, the description adequately explains the score's range, its meaning, and the dimensions checked. It does not describe the url parameter's expected format, but otherwise gives enough context to call the tool correctly. Annotations cover the safety profile.

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 0% and the only parameter (url) has no description in the schema. The description implies the parameter points to a public business website, but adds no format details, examples, or constraints. It barely compensates for the missing schema documentation.

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 produces a 0-100 score of a public business website's agent-readiness, listing the specific dimensions it evaluates (AI crawler rules, llms.txt, schema.org data, etc.). It also distinguishes itself from a Google ranking score. However, it does not explicitly differentiate from sibling tools like ai_crawler_audit or agent_ready_fix_pack.

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 gives no guidance on when to use this tool versus alternatives. It mentions it is free and not a Google ranking, but does not say when to choose it over agent_ready_fix_pack or ai_crawler_audit, nor does it state any prerequisites or exclusions.

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