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 externally. The description adds nothing beyond a pointer to describe_operation for request schemas; it does not describe what data is returned or any behavioral nuance.

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 core sentence is duplicated verbatim, so half the text is pure waste, and the remaining content (operation ID, describe_operation pointer) is not front-loaded with any explanation of purpose.

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?

With 0% schema coverage, no output schema, nested query object, and an ambiguous 'id' parameter, the description should carry substantial explanatory weight but delivers only the endpoint path. An agent cannot confidently invoke this correctly without first calling 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 neither parameter is described anywhere. The path mentions ':leaseId' and ':id', but the description never explains what 'id' refers to (a supplemental rent record id?) or the relationship between the two identifiers, leaving both parameters semantically ambiguous.

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 essentially the raw endpoint path 'GET /api/leases/:leaseId/supplemental-rent/:id/monthly-sales' repeated verbatim twice. It does identify the resource (monthly sales under a lease's supplemental rent) and distinguishes it from siblings like the other supplemental_rent sub-resources by path, but it offers no plain-language statement of what the operation returns or does.

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 tool versus the ~11 sibling supplemental-rent tools or 'describe_operation'/'search_operations'. The only directive is 'describe_operation provides native request schemas', which is a schema-fetch hint, not usage guidance.

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