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

Adds significant context beyond annotations: FREE (no credits), UTF-8 encoding requirement, exact save instructions, and the Google disavow syntax. Annotations already cover read-only/idempotent safety; the description adds operational details about the output artifact itself.

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?

Single dense sentence pack with the critical output format front-loaded, followed by syntax definition and save instructions. No waste, every clause earns its 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?

For a single-parameter read-only export tool, the description covers everything needed: what it does, the output format, the syntax rules, encoding, and the downstream usage pattern. With annotations covering safety profile, no further behavioral disclosure is required.

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 coverage is 100%, so the projectId parameter is fully documented in the schema including how to obtain it. The description doesn't add parameter-specific meaning beyond what's in the schema — baseline 3 is appropriate.

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 (export) and resource (disavow file) and precisely defines what the output represents — the exact .txt content Google's disavow tool accepts. This distinguishes it from siblings like list_disavow_entries, which lists entries rather than producing a Google-ready file.

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?

Provides context about free usage and the output format, but doesn't explicitly state when to use this vs list_disavow_entries or add_disavow_entry. Usage is implied rather than spelled out.

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