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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no mention of side effects, whether anything is persisted or sent, permission or auth needs, or what a response contains. 'Write' in the name suggests a mutation, but the description never confirms or qualifies that, leaving the risk profile entirely unknown.

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?

It is only two sentences and not padded, but the second sentence is pure marketing boilerplate that earns no place in a tool definition. The informative content is essentially zero, so brevity here reflects under-specification rather than discipline.

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?

The tool is structurally simple (one optional string, no output schema, no annotations), which lowers the bar, but the description still fails to convey the one thing an agent needs: what calling it produces. The 'prompt pack' framing obscures whether this returns a complaint draft, a template, or instructions.

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% and the single optional 'query' parameter is documented in the schema itself. The description adds no meaning beyond it, such as what scoping a query actually changes. Baseline 3 applies when the schema already does the work.

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 description restates the name ('complaint write tool system') and then pivots to product-marketing language ('delivered as a copy-paste prompt pack with examples') rather than stating what the tool actually does. It never says whether it drafts a complaint, classifies one, or generates a reply. With nine sibling complaint-* tools (gen, rewrite, polish, reply, sort, audit), the agent gets no basis for choosing this one.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative among complaint-gen-tool, complaint-rewrite-tool, complaint-polish-tool, or complaint-reply-tool. 'Run today' is sales copy, not a usage condition. The agent must infer selection 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.