check_robots

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

Discloses read-only nature, single HTTP GET, no auth, no rate limits, deterministic, rule-based, no LLM. Lacks details on error handling or limits (e.g., timeout), but overall informative.

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?

Well-structured with clear sections: main action, behavioral traits, usage guidelines. Every sentence adds value. No redundancy or fluff.

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 single-parameter tool with no annotations or output schema, the description covers purpose, behavior, usage, and distinguishes from siblings. Sufficient for an agent to use correctly.

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 100% (baseline 3). The description adds value by explaining the parameter's input formats and the tool's actions (fetch /robots.txt, report per-crawler posture), going beyond 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 clearly states the tool's purpose: 'Fetch and parse a domain's robots.txt; report per-crawler allow/disallow posture.' It specifies the exact resource and action, and distinguishes itself from siblings like 'check_sitemap' and 'audit_page'.

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?

Explicit guidance on when to use: 'figuring out which AI crawlers a site blocks vs allows.' Suggests combining with 'check_sitemap' and contrasts with 'audit_page', providing clear context for decision-making.

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