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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action (fetch) and the result (group counts), but does not explain what 'group counts' means, whether the fetch is synchronous, error handling, rate limits, or any side effects. Moreover, the parameter schema suggests behaviors (normalization, validation, timezone checks) that are completely unrelated to fetching a robots.txt, so the description fails to clarify the actual behavior.

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 sentence, which is concise and front-loaded with the main action. However, it is misleading because the parameters do not support the stated behavior, and it does not mention the parameter mismatch. The brevity is not a virtue when it omits crucial clarification about the tool's actual inputs.

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 tool with no output schema, no annotations, and four parameters that appear unrelated to the description, the description is grossly incomplete. An agent has no idea how to supply the parameters to fetch a robots.txt, what a 'group count' is, or what the return format looks like. The description fails to bridge the gap between the stated purpose and the actual interface, making the tool effectively unusable without additional investigation.

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 description says nothing about any of the four parameters, so it adds no meaning beyond the schema. Although schema coverage is 100%, the schema descriptions (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate') describe tasks that are not related to fetching a robots.txt, leaving the agent unable to map the parameters to the stated purpose. The description should have explained how url, host, json, and zone relate to robots.txt inspection, but it does not.

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 states a clear verb and resource: 'Fetch a public robots.txt and return group counts only.' This is specific and differentiates it from siblings, which all appear to handle other tasks like normalization or validation. However, the parameter names and their schema descriptions (URL normalization, JSON validation, timezone) do not align with this stated purpose, creating confusion about what the tool actually does.

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?

There is no guidance on when to use this tool versus the siblings. The description does not mention any exclusions, alternatives, or conditions for selection. Given the sibling set (normalize-url, validate-json, timezone, etc.), an agent would have no way to know this tool is for robots.txt inspection rather than those other tasks.

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