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

No annotations are provided, so the description carries the full burden. The only behavioral hint is that output arrives as 'a copy-paste prompt pack with examples', which leaves unclear whether any real generation occurs, whether the query scopes anything, or what the caller receives. For a tool with zero annotation coverage that is a substantial gap.

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 both sentences are marketing filler rather than specification: 'production-ready', 'repeatable workflow', 'run today' consume the space where the actual function should be stated.

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 output schema and no annotations, the description is the only source of behavioral truth, and it does not explain what a call produces or how the query affects it. The 'prompt pack' framing even muddies whether this is a generator at all.

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 coverage is 100% for the single optional 'query' parameter, so the baseline is 3. The description adds no meaning about how the query scopes output, though with one well-documented optional parameter little is missing.

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 restates the tool name ('contract gen tool system') and pads it with audience framing ('marketing and operations leaders') and marketing language ('production-ready', 'run today'). It never says what the tool actually does to a query, nor whether it drafts, templates, or merely returns a prompt pack, so it cannot be told apart from siblings like contract-write-tool or contract-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, when-not-to-use, or named alternative. 'You can run today' is promotional rather than a usage condition, and the crowded contract-* sibling family means routing guidance is exactly what this definition should supply.

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