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 externally. The description adds no behavioral context such as pagination, authorization requirements, or what the sales records represent, so it contributes nothing beyond the annotations.

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 description is short but wastes its first two sentences by repeating the identical endpoint path verbatim. The only non-duplicated content is a schema pointer, so nothing is front-loaded except the raw route.

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?

This is a nested-object, undocumented-parameter read tool with no output schema and many confusingly similar siblings. A description that only restates the route and refers vaguely to describe_operation leaves the agent without enough information to invoke 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% for two required path parameters plus an untyped query object, and the description provides no semantics for leaseId, id, or allowed query filters. It merely echoes the path template, leaving the agent to infer what each parameter identifies.

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 merely repeats the endpoint path twice and gives an operation ID; it does not explain what 'sales' data is or what the tool returns. It does convey the verb (GET) and resource path, but the purpose is effectively a tautology of the name and title.

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 use this tool versus the eleven sibling supplemental-rent GET tools or the supplemental-rent dashboard. The only pointer is that 'describe_operation provides native request schemas,' which is a schema hint, not usage guidance.

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