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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries the behavioral burden. It never says whether the playbook persists, whether it can be edited later, whether the name must be unique at creation time, or what happens on validation failure for red lines or duplicate clauseIds.

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 dense sentence that front-loads the action and lists the meaningful clause-level fields with their ranges. No filler, though the enumeration is a bit list-like rather than prioritizing what matters most.

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?

For a mutation tool with no output schema and only weak annotations, the description omits when to use it, whether playbooks are reusable or editable, and how the required top-level parameters interact with the entries array. An agent can form the call but lacks context to use it correctly.

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 only 40%, but the description usefully expands the nested 'entries' semantics (preferred option, priority 1-5, flexibility 1-5, red lines, acceptable alternatives) beyond the bare schema. It says nothing about name, contractType, governingLaw, or contractLanguage, so it only partially compensates for the coverage gap.

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 states a specific verb and resource ('Create a negotiation playbook') and enumerates the per-clause content it captures. However, it never distinguishes this tool from negotiation-oriented siblings like initiate_negotiation or explain_options, so an agent gets no routing help.

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 create a playbook versus alternatives, no prerequisites, and no exclusions. The agent must infer usage entirely from the verb.

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