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 fully covered elsewhere. The description adds nothing about the response shape, permissions, or errors — only the pointer to describe_operation — so it contributes almost no behavioral context beyond structured data.

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 endpoint string is repeated verbatim twice before any other content, which is pure waste, and the remaining text is an operation ID plus a pointer to another tool. Nothing is front-loaded as a human-readable purpose statement.

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 read tool with no output schema and 0% parameter documentation, the description should at least characterize what the summary contains and disambiguate 'id'. With annotations only covering safety and no return description, an agent knows the route but not the payload or when this is the right call among dozens of supplemental-rent siblings.

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%, so the description carries the burden for the two path parameters. The URL template does positionally indicate that leaseId scopes to a lease and id identifies a supplemental-rent record, but neither is named in prose and no format, uniqueness, or lookup semantics 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 essentially the raw endpoint path, which does encode a clear verb (GET) and resource (supplemental-rent summary for a given lease and record id), so an agent can distinguish it from sibling supplemental-rent endpoints by the trailing 'summary'. However, it never explains in plain language what a 'supplemental rent summary' returns, leaving the purpose to be inferred from URL structure.

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 choose this over the many sibling supplemental-rent tools (e.g., the other supplemental_rent variants or the portfolio/dashboard tools). The only actionable hint is that describe_operation can supply native request schemas, which is a workflow note rather than a usage rule.

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