robots_check

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

In absence of annotations, the description discloses the POST method, 402 error for unpaid requests, and payment mechanism (USDC on Base). It doesn't cover rate limits or other edge cases, but addresses critical behavioral traits.

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?

Two sentences with no redundancy. First sentence defines core purpose concisely; second sentence adds essential payment context. Every sentence earns its place.

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 tool with 1 parameter and no output schema, the description covers purpose, behavior, and payment requirement fully. No gaps for agent decision-making.

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 covers 100% of the single 'url' parameter. Description adds no additional meaning beyond the schema description 'Any URL on the site', thus baseline score applies.

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 fetches robots.txt and llms.txt, reports AI crawler status, and includes sitemaps, using a specific verb 'Fetch' and distinct resource. It differentiates from siblings like 'headers_check' or 'seo_audit'.

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 for checking AI crawler permissions and sitemaps, and notes payment requirements. It lacks explicit when-not-to-use or alternative tools, but the uniqueness of the tool makes usage context clear.

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