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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond them: no mention of what the compliance payload contains, whether it requires a specific lease/term state, or error behavior for unknown termId.

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 sentence appears twice back-to-back, which is pure waste; the useful content is a single fragment about `describe_operation`. There is no front-loaded statement of what the call is for.

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?

No output schema exists, so the description should explain what a 'compliance' result contains, yet it says nothing. For a nested-parameter, domain-specific endpoint in a large API surface, an agent is left without enough to call it confidently.

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 the description does not explain what `leaseId` and `termId` identify beyond their position in the path template. With two undocumented path parameters, the description should have compensated but only mirrors the URL pattern.

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 tool title repeated verbatim: a raw REST path plus operation ID. The path does encode resource nouns (leases, supplemental-rent, compliance), so an agent can guess it retrieves compliance data for a supplemental rent term, but nothing states that in words or distinguishes it from the many sibling `get_leases_by_leaseId_supplemental_rent_*` endpoints.

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 endpoint versus the dozen-plus other supplemental-rent siblings. The only routing hint is that `describe_operation` provides native request schemas, which is a schema-lookup instruction, not usage guidance.

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