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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only lists output contents and does not explain whether q is a domain or URL, whether the tool performs a live fetch, or what happens when q is omitted.

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 very short, but it is under-specified rather than elegantly concise. It omits the action and the parameter, so the text reads more like a label than a usable tool description.

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 one-parameter tool in a large sibling list, the description lacks the parameter semantics and usage context needed to invoke it correctly. The presence of an output schema may cover return values, but it does not compensate for missing invocation guidance.

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 schema has one undocumented q parameter with 0% schema description coverage, and the description never mentions q at all. An agent cannot infer whether q expects a domain, a complete URL, a search term, or something else.

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 fragment names the exact resource (robots.txt) and its relevant contents (disallowed paths + sitemaps), which is more specific than a tautology and distinguishes it from nearby tools like robotsmeta and sitemap. It lacks an explicit verb like 'fetch' or 'parse', but the intended purpose is reasonably clear.

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?

No sentence tells an agent when to choose robots over robotstxt_history, robotsmeta, or the many sitemap-related siblings. The content hint implies a robots.txt parsing use case, but no conditions, exclusions, or alternatives are provided.

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