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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile requires no description support. The description adds no behavior beyond that—no pagination, filtering, or return-shape context—only a referral to describe_operation.

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 appears twice back-to-back, which is pure duplication, and the one genuinely useful clause (the describe_operation referral) is buried at the end.

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 tool with 0% schema description coverage and no output schema, the description supplies nothing an agent needs—no parameter meaning, no response expectation, no distinction from its many near-identical 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% for two required path parameters. The URL template at least reveals that `leaseId` is a lease identifier and `id` is a supplemental rent record identifier, which is some semantic value, but no formats, constraints, or query-object usage are explained.

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 a verbatim restatement of the tool title/endpoint path, duplicated twice with no natural-language explanation. The path does imply 'fetch fiscal accruals for a supplemental rent record under a lease', but nothing states the purpose in words an agent can reason about.

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?

No indication of when to use this endpoint versus the dozens of sibling `get_leases_by_leaseId_supplemental_rent_*` tools. The only guidance is a pointer to `describe_operation` for the native schema, which is about payload shape, not usage selection.

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