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 covered. The description adds nothing beyond annotations — no mention of pagination, filtering, empty-result behavior, or response shape for what is presumably a list endpoint.

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 path string is duplicated verbatim with no content between them, wasting the small budget the description does have. It is short but not front-loaded with information beyond the raw endpoint path.

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 two-parameter, nested-object GET with 0% schema coverage and no output schema, the description leaves an agent without enough to call the tool correctly. The describe_operation pointer is the only bridge and it shifts the real documentation burden elsewhere.

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 two parameters (a nested required 'id' plus a free-form 'query') are undocumented. The description does not explain what 'id' refers to or what the arbitrary 'query' object supports, though it does point to describe_operation as the place to obtain native request schemas.

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 a verbatim restatement of the tool title/path ("GET /api/leases/:id/payments") repeated twice. It technically implies fetching payments for a lease, but it adds no purpose beyond the name and draws no distinction from the many neighboring lease sub-resource tools.

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 guidance on when to use this versus siblings such as get_leases_by_id_payment_requests or the accounting lease payment schedule endpoints. The only actionable hint is the pointer to describe_operation for native schemas, which is a schema-access note rather than usage guidance.

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