geo_check_robots

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

Description discloses the specific bots checked (GPTBot, ClaudeBot, etc.), implying a read-only check. With no annotations, it adequately covers the behavioral traits for a simple query tool.

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 concise sentences: first gives usage imperative and purpose, second adds detail. Front-loaded and free of redundancy.

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 the simplicity (1 param, no output schema), the description covers when and what it does adequately. Lacks error handling details but sufficient for a fast check tool.

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 only parameter 'url' is not described in the schema (0% coverage), but the description adds 'Requires a URL', providing the needed semantic context.

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 explicitly states the tool checks robots.txt for AI bot access, and distinguishes from sibling 'geo_score' by positioning it as a fast first check before a full 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?

Clear when-to-use instruction: 'ALWAYS use this tool when the user asks specifically about robots.txt, AI bot access, or which crawlers are allowed or blocked.' Also advises on pre-check vs full audit with geo_score.

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