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

With no annotations, the description carries the full behavioral burden, and it delivers marketing claims instead: "Save hours every week" and "battle-tested" convey no information about output format, length, side effects, or determinism. Nothing tells an agent what a call returns or what happens to the optional query, so an agent cannot predict the result before invoking it.

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 short, but every sentence is promotional filler rather than operational content. The lead sentence, "Save hours every week," is pure advertising and pushes out any statement of what the tool does.

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?

This is a simple one-parameter tool, so full completeness is achievable in a sentence or two, yet the description omits the output artifact entirely and never clarifies whether the result is a handover document, a prompt template, or a playbook. An agent cannot decide to call it based on this text alone.

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?

The tool has one optional parameter with 100% schema description coverage, so the schema already explains that "query" scopes the analysis. The description adds no meaning to it, but the baseline of 3 applies when the schema does the documenting.

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 never states what the tool actually produces. "Handover gen" implies generating handover documents, but the text describes a "prompt and operating playbook for restaurant/brand growth," which is a different artifact and an unexplained domain narrowing. It also fails to distinguish itself from the many handover siblings (handover-write-tool, handover-tpl-tool, handover-summary-tool, handover-audit-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?

No when-to-use guidance, no prerequisites, and no mention of any alternative. The only usage-adjacent claim, "No setup, works in any LLM chatbot," says nothing about which task or input should trigger this tool over the dozen other handover tools.

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