Robots.txt Generator

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that output is derived purely from the supplied rules and sitemaps, but says nothing about output format, ordering, or how conflicting allow/disallow entries are resolved.

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?

A single front-loaded sentence with no filler. Every clause corresponds to a real input of the tool.

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 generator with no output schema, the description should at least say what it returns (e.g. the robots.txt text) and note required fields. It covers inputs adequately but leaves the return shape and required-parameter behavior unspecified.

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 0%, so the description carries the burden. It does map the two top-level params ('allow/disallow rules' and 'sitemap URLs'), but omits crawlDelay, userAgent matching/wildcards, and the required nested userAgent field, leaving meaningful gaps.

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 and artifact ('Generate a robots.txt') plus the input sources (per-user-agent allow/disallow rules, sitemap URLs). An agent can distinguish it from xml_sitemap_generator by the output artifact, though the description never explicitly contrasts the two.

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 when-to-use guidance, no prerequisites, and no alternatives named despite a crowded sibling set of SEO generators. The agent must infer that this is the tool for robots.txt rather than xml_sitemap_generator from the name alone.

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