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 structurally. The description adds nothing beyond that — no note on what 'pending' means, whether results are paginated, or what determines pending status.

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 sentence is duplicated back-to-back, and an opaque Operation ID is included, which is noise for an agent. There is no front-loaded statement of what the tool returns or when to call it.

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 no output schema, 0% parameter description coverage, and a nested/free-form 'query' object, the description should carry the burden of explaining the identifier and query semantics — it does none of that. An agent could construct the call but would not know what 'pending' filters or what shape to expect.

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 2 parameters (a required string 'id' and an untyped free-form 'query' object). The only semantic hint is the ':id' placeholder in the URL, implying the lease identifier, but neither 'id' format nor the accepted 'query' keys are explained anywhere.

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 endpoint path and title verbatim ('GET /api/leases/:id/rent-schedules/pending' appears twice). An agent can infer 'fetch pending rent schedules for a lease' only from the raw URL tokens, not from any explanatory sentence. It does not distinguish this from the many sibling lease rent-schedule tools (e.g. get_leases_by_id_rent_schedules_by_sche...).

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 use this tool versus the numerous other lease rent-schedule and pending-item siblings (get_reassessments_pending, get_terminations_pending, etc.). The only routing hint is 'describe_operation provides native request schemas', which points to a discovery tool rather than giving usage criteria.

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