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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no auth requirements, no pagination, no note about what supplemental rent data comprises — apart from the describe_operation breadcrumb.

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 REST path sentence is repeated twice verbatim, which is pure waste; only the operation ID and the describe_operation pointer add anything. Front-loading is fine but the duplication signals auto-generation rather than deliberate drafting.

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-object, 0%-coverage, no-output-schema read tool, the description should explain what supplemental rent records contain and how the query object is used. It instead defers entirely to describe_operation, leaving the agent unable to call the tool confidently without a second round trip.

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% for the two parameters, so the description carries the full burden and fails. The path template implies leaseId is a lease identifier, but the free-form 'query' object is never explained, and no constraints or accepted filters are given.

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 REST path 'GET /api/leases/:leaseId/supplemental-rent', which does convey a verb and a resource (supplemental rent data scoped to one lease). It never states in plain language what the endpoint returns or how it differs from the many other supplemental-rent siblings, so the agent must infer purpose from syntax alone.

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 guidance is that 'describe_operation provides native request schemas' — that is a pointer for schema discovery, not a when-to-use rule. There is no indication of when to prefer this over the 10+ sibling get_leases_by_leaseId_supplemental_rent_* tools or view_supplemental_rent_dashboard.

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