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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own — no auth requirements, no note on what the draft contains or whether it may be absent.

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, but the first sentence is duplicated verbatim, which is pure waste rather than front-loading. The remaining content is an operation ID and a pointer to another tool.

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 nested-params GET with no output schema and no documented parameters, the description leaves the agent unable to predict what the draft endpoint returns or how it differs from its three siblings. The describe_operation pointer is the only thing preventing a score of 1.

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 0%, so the description must carry parameter meaning, and it does not. The path template :entity/:id only echoes the two required parameter names; it never explains what values 'entity' accepts (e.g., lease, contract) or what 'id' identifies.

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 is the raw endpoint path repeated twice, which merely restates the name and title. Nothing explains what a 'draft' negotiation resource is, so an agent cannot distinguish this from the sibling tools get_negotiation_by_entity_by_id_current, _redline, and _version.

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 the draft variant versus current, redline, or version. The only usable pointer is 'describe_operation provides native request schemas', which directs the agent to a schema lookup tool rather than explaining selection criteria.

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