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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds nothing beyond that — no mention of pagination, date-range behavior, auth requirements, or what the response contains — even though it defers to describe_operation for request details.

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 and padded with an opaque operation hash. It is short but the content is redundant and does not front-load anything useful about the endpoint.

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 an undocumented open-ended query object with no output schema and no annotations describing return shape, the description supplies nothing about inputs or outputs. It is not sufficient for an agent to call the tool correctly without a follow-up describe_operation call.

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 free-form 'query' object accepts arbitrary properties with no documentation anywhere. The description provides zero meaning for either parameter, leaving the agent to guess at filter keys.

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 only restates the tool name as an HTTP path ('GET /api/calendar/payments') twice, which is a tautology rather than an explanation. It never says what these payments represent (lease payments? calendar-linked disbursements?), how they differ from get_calendar_events, or what scope they cover.

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?

The only actionable sentence routes the agent to describe_operation for native request schemas, which is a pointer, not usage guidance. There is no statement of when to call this versus siblings like get_calendar_events or get_leases_by_id_payments.

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