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

Annotations declare readOnlyHint=false, correctly signaling a write, but the description adds nothing behavioral beyond that: it does not say whether name collisions fail or overwrite, whether the created playbook is immediately usable, or what happens on partial/invalid entries. For a pure mutation with no output schema, this is a notable 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?

A single front-loaded sentence with no filler; every clause carries information about the payload shape. Slightly dense but appropriately sized.

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 40% schema coverage, a create tool needs more transactional detail (unique-name behavior, required discovery of clause/option IDs, validation failures) than is provided. The entry-level semantics are covered, but the creation workflow is only minimally complete.

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 only 40%, but the description partially compensates by unpacking the nested entries fields (preferred option, priority 1-5, flexibility 1-5, red lines, acceptable alternatives). It says nothing about the required top-level fields name, contractType, governingLaw, or contractLanguage, leaving those to the schema.

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?

States a specific verb (Create) and resource (negotiation playbook) and enumerates the clause-level preferences it defines. It is clearly distinguishable from siblings like generate_contract or initiate_negotiation, though it does not explicitly name them.

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 guidance on when to use this tool versus alternatives such as initiate_negotiation, nor any prerequisites (e.g., that clause/option IDs and contract types must be discovered first via list_contract_types or list_templates). The agent must infer the setup workflow entirely.

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