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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds no behavioral context at all — not what a reconciliation record contains, whether it can be missing, or whether the id refers to the reconciliation or the supplemental-rent record.

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 only substantive sentence is duplicated word-for-word, which is pure waste rather than front-loading. The operation-ID/describe_operation note is useful but buried after the repetition.

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, a nested params object, 0% parameter documentation, and a dense sibling namespace of near-identical supplemental-rent GETs, the description leaves the agent unable to distinguish this call or interpret its ids. Only the annotations and the describe_operation pointer prevent a floor score.

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, and the description does not compensate. It never explains that leaseId is the lease identifier nor disambiguates the ':id' — it is unclear whether that id identifies the reconciliation, the supplemental-rent line, or a period.

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 endpoint path repeated verbatim, which merely restates the tool name and title rather than explaining what a supplemental-rent reconciliation resource is or what reading it yields. An agent learns nothing beyond the URL shape already encoded in the name.

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 fetch this reconciliation versus the many sibling supplemental-rent endpoints (portfolio, import targets, dashboard) or versus describe_operation/search_operations. The only hint is the trailing pointer to describe_operation for request schemas, which is a schema-location note, not a usage rule.

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