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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and generating text rather than writing a file is consistent with readOnlyHint. The description adds the meaningful scoping fact that all documented AI crawlers are enumerated, plus the REST equivalence, but says nothing about determinism of output, the meaning of 'a policy', or how defaults are applied. Some added value, no contradiction.

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 short sentences with zero filler, and the core purpose is front-loaded in the first sentence. The second sentence earns its place by mapping the tool to a known HTTP endpoint.

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 7-parameter, all-optional generator with no output schema, the description covers what it produces but not the shape of the returned text (headers, ordering, whether it is copy-pasteable). It also leaves the loose 'allow or block' string typing entirely to the schema, which is adequate but not compensating for anything.

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 description coverage is 100%, so all seven parameters (path, search, signals, sitemap, datasets, training, user_fetch) are documented in the schema with their defaults. The description contributes no additional parameter meaning, such as how 'search' relates to 'signals' or that the allow/block strings are the only accepted values.

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?

States a specific verb (generate) and resource (robots.txt) plus the distinctive scope: it names every documented AI crawler and encodes an explicit allow/block policy. The phrase 'Same as GET https://bozos.si/api/v1/robots' clarifies it produces the file content. It does not, however, name or contrast with the sibling checkRobotsTxt, which is the most likely confusion point.

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?

Usage is only implied: the agent can infer 'use this when you need to author a crawler policy' from 'for a policy', but there is no explicit when-to-use or when-not-to-use statement, and no routing to checkRobotsTxt for the validation case or to planAgentRetrieval for the planning case.

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