check_robots

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

Describes read-only nature, single HTTP GET, no auth/rate limits, deterministic rule-based analysis with no LLM. Since annotations are absent, this fully discloses 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?

Well-structured with clear sections but slightly verbose; could tighten phrasing without losing meaning. Front-loaded with primary purpose.

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 low-complexity tool with one parameter and no output schema or annotations, the description covers purpose, usage, behavior, and parameter adequately, leaving no significant gaps.

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% and the schema already describes the domain parameter in detail. The description adds only minor context about returned per-crawler status, but baseline 3 is appropriate as parameter understanding is sufficiently supported by 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?

Description clearly states it fetches and parses a domain's robots.txt and reports per-crawler allow/disallow posture for AI crawlers. It distinguishes from sibling tools like check_sitemap and audit_page, making the purpose specific and unambiguous.

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 provides 'When to use' guidance: figuring out AI crawler blocks. Recommends combining with check_sitemap for full audit and distinguishes from audit_page, offering clear context for when to choose this tool.

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