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

No annotations are supplied, so the description carries the full disclosure burden and largely fails it: it never says whether the tool mutates a source document or produces new text, what permissions or inputs it needs, or how large an input it accepts. The one behavioral hint is that the deliverable is a 'copy-paste prompt pack with examples', which is vague about actual output shape.

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?

Two sentences, but both are front-loaded with audience and bragging ('production-ready', 'you can run today') rather than the function. Practically every phrase is promotional filler that does not help an agent decide or invoke.

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 annotations, no output schema, and a large ambiguous sibling family, the description needed to explain purpose, input expectations, and output form. Instead it offers only a product pitch, leaving an agent unable to determine what the tool returns or when to prefer it.

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?

There is a single optional 'query' parameter whose meaning is fully documented in the schema (100% coverage), so per the baseline the schema does the work. The description adds nothing about how a query scopes the rewrite, but it also does not mislead.

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 tool name ('handover rewrite tool') and wraps it in marketing language ('production-ready... system for marketing and operations leaders') without stating what operation it performs — rewriting a handover document? generating one? It never gives a specific verb+resource beyond the name itself, and an agent cannot tell it apart from handover-polish-tool or handover-write-tool from this text.

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 at all: no trigger conditions, no prerequisites, and no mention of the eight sibling handover-* tools (audit, check, gen, polish, reply, sort, summary, write) it must be distinguished from. 'Run today' is sales copy, not selection guidance.

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