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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and open-world access, so the safety profile is covered. The description adds real value beyond them: the exact set of edits applied, the guarantee that 'nothing else is touched', and the fact that every change is surfaced at the top of the result. It stops short of clarifying whether the corrected file is returned as text or written anywhere.

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?

Front-loaded with the core object ('The domain's served robots.txt, corrected') and followed by a compact enumeration of the three repair classes plus the reporting behavior. Dense but no sentence is wasted; the parentheticals earn their place.

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?

With no output schema, the description usefully states the return shape (corrected content with a change list at the top) and annotations cover safety and idempotency. The remaining gap is the domain parameter's accepted format, which is undocumented in both schema and description.

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?

One parameter with 0% schema description coverage, so the description carries the burden of explaining 'domain'. It establishes that the parameter identifies the domain whose served robots.txt is fetched, but never states the expected format (bare hostname vs. URL vs. path). Partial compensation only.

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?

Names a specific resource (the domain's served robots.txt) and enumerates exactly what 'corrected' means: shadowing group rules copied into named groups, a Sitemap line added, and a minimal replacement for HTML responses. An agent knows precisely what transformation is performed. It stops short of naming a sibling (e.g. resolve_robots for the raw file), so it is not a 5.

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?

The enumeration of repairs implies the tool is used when a robots.txt is malformed or incomplete, so usage is inferable. However, there is no explicit when-to-use statement and no routing against resolve_robots (raw fetch) or scan_domain, which is the main decision an agent faces in this sibling set.

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