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

No annotations are provided, so the description carries the full burden. It hints that the deliverable is "a copy-paste prompt pack with examples", which is the only behavioral signal, but says nothing about side effects, required inputs, permissions, or what is actually returned for a 'write' tool.

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?

Only two sentences, but both are marketing copy rather than functional description; filler like "production-ready" and "structured, repeatable workflow you can run today" crowds out what the tool actually does. The functional core is not front-loaded.

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, no-annotation, no-output-schema tool, the description should at minimum state what artifact the tool produces and when to invoke it. Instead it reads as a sales pitch, leaving the agent unable to predict the result of a call.

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 fully documented in the schema (100% coverage), so the schema does the work. The description adds no meaning about how 'query' scopes the output, so it neither helps nor harms beyond the baseline.

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 largely restates the tool name ("handover write tool system") and wraps it in promotional language ("production-ready", "for marketing and operations leaders") rather than stating a concrete verb and output. It never clarifies what a 'handover write' produces or how it differs from the many sibling handover-* tools such as handover-gen-tool or handover-tpl-tool.

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 reference to any alternative. The phrase "workflow you can run today" implies general applicability but gives the agent no basis for choosing this tool over handover-gen-tool, handover-polish-tool, or handover-tpl-tool.

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