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 by structured data. The description adds nothing beyond that: no mention of pagination, filtering behavior, the shape/nesting of the disputes result, or what an unknown leaseId yields. It does not contradict the annotations, but it contributes no behavioral context of its own.

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?

The same sentence is duplicated verbatim, which is pure waste, and the useful content (operation ID and the describe_operation pointer) is buried after the repetition. The text is short but under-specified rather than concise.

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?

The tool has a nested open-ended query object, 0% schema coverage, and no output schema, so the description carries a heavy burden and delivers almost none of it. It gives no indication of what a disputes collection contains or how to scope it, leaving an agent unable to call it correctly without first invoking describe_operation.

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% and the description explains neither the required leaseId path parameter nor the free-form 'query' object (an open object with additionalProperties {}). The only signal, ':leaseId' inside the route string, merely restates the schema key. The 'describe_operation' pointer is a marginal compensating hint but leaves the agent without any semantics for filtering or query parameters.

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 route restated twice: 'GET /api/cam/leases/:leaseId/disputes.' It does hint at the resource (disputes scoped to a lease), but it reads as a tautological echo of the tool name/title rather than an explanation of what the tool returns or does. Nothing distinguishes it from the many sibling lease sub-resource getters beyond the literal path segment.

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 call this versus alternatives such as get_cam_leases_by_leaseId_notes or the other lease sub-resource endpoints. The only actionable guidance is the pointer that 'describe_operation provides native request schemas', which tells the agent how to learn the request shape but not when this tool is the right choice.

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