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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about what invocation actually does, whether output is a prompt or a finished contract, what inputs are needed, or side effects. The "includes the complete prompt, usage guide, and edge-case handling" line describes pack contents, not tool 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?

It is short and front-loaded, but the opening sentence is a slogan rather than an operative statement, so the useful part (a restaurant/brand prompt pack) arrives unfocused. Nothing is padded, yet little of it earns its place.

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 only a vague one-parameter schema, the description needed to carry the burden of how the tool behaves and returns. Instead it reads as product copy, leaving an agent unable to predict the result of calling it or to choose it over contract-gen-tool or contract-tpl-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?

There is a single optional parameter whose meaning is fully documented in the schema ("Optional user query to scope the analysis."), so the schema does the work. The description adds nothing further, but with 100% coverage and a trivial param surface, the baseline is high.

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 largely restates the name ("contract write tool") behind marketing framing ("Turn expertise into output", "prompt pack", "professional results in minutes") without stating the actual operation. It never clarifies whether it drafts a contract, generates a prompt, or fills a template, and it does nothing to distinguish itself from siblings like contract-gen-tool, contract-tpl-tool, or contract-rewrite-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?

The only scoping hint is an audience ("restaurant and brand teams"), which is context, not usage guidance. There is no when-to-use, no when-not-to-use, and no routing to any of the many alternative contract-* tools.

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