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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing about behavior, output, side effects, or limits. Claims like 'no prompt engineering needed' and a '30-day support promise' are commercial messaging, not operational behavior.

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?

Three sentences of promotional copy with no functional statement front-loaded; none of the wording helps an agent decide whether to call the tool. Under-specification rather than genuine conciseness.

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 description that describes a purchasable kit instead of an operation, an agent cannot determine what calling this tool returns or how to use the one parameter. Completely inadequate for even a one-parameter tool.

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 single optional 'query' parameter is fully documented in the schema, so the baseline is 3. The description adds no meaning beyond it and never mentions how the query scopes or shapes the result.

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 text frames the tool as an 'AI-powered restaurant & brand intelligence pack' and a 'prompt kit with step-by-step instructions,' which does not describe an invocable contract-reply operation and reads as unrelated marketing copy for the name contract-reply-tool. The only nod to purpose is the phrase 'contract reply tool workflow,' which merely restates the name without saying what the tool actually does with a query.

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 guidance on when to use this tool, when not to, or which of the many siblings (contract-check-tool, contract-polish-tool, contract-rewrite-tool, complaint-reply-tool, etc.) to prefer under what conditions. An agent has no basis for routing.

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