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

With no annotations supplied, the description carries the full burden of disclosure, yet it reveals nothing about what happens on invocation, what is returned, whether anything is mutated, or any permission or rate constraints. The '30-day support promise' and 'step-by-step instructions' describe a product bundle rather than tool behavior, leaving the agent with zero operational context.

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 which only the second touches on function while the first and third are marketing filler about prompt kits and support promises. The purpose is not front-loaded and the customer-facing tone wastes the limited space that should explain behavior.

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 has one optional parameter, no annotations, and no output schema, so the description must explain what the agent gets back and how to frame the query; it does neither. What remains is a product pitch, leaving the definition inadequate for correct invocation despite the tool's low complexity.

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 description coverage is 100% and the single parameter is an optional string already documented in the schema as 'Optional user query to scope the analysis.' The description adds no meaning beyond that, but per the high-coverage baseline a 3 is appropriate rather than a penalty.

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 calls itself a 'restaurant & brand intelligence pack' and then says it generates a 'contract audit tool workflow', which mixes two unrelated domains and never states what the tool actually does when invoked. 'Generate a ready-to-use workflow' is the only verb-and-resource pair, and it describes a prompt kit being delivered, not an analysis being performed, so an agent cannot tell this apart from contract-check-tool, contract-gen-tool, or contract-summary-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 statement of when to use this tool, when not to, or which of the many contract-* siblings to prefer. 'No prompt engineering needed' is sales language, not usage guidance, and the lone optional parameter provides no selection criteria.

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