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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that — no indication of permissions required, whether the report is computed on the fly, or what happens with an invalid leaseId/id combination. No contradiction with 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 defining sentence is duplicated verbatim, and the operation ID hash adds no meaning for an agent. Brevity here reflects under-specification rather than efficiency — nearly every sentence is either a repeat or a machine-generated identifier.

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 parametrized GET with a nested params object, 0% schema description coverage, and no output schema, so the description must do real work. Instead it supplies no information about the returned report, its scope, or the ambiguity between the two string identifiers, leaving an agent able to find the endpoint but not to use 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%, so the description carries the full burden, yet it only implicitly echoes the two path placeholders (:leaseId and :id) that already appear in the title. It never clarifies what 'id' identifies (a supplemental-rent record id vs. a report id) or what the free-form 'query' object supports, leaving the nested params object under-specified.

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 endpoint path restated twice ('GET /api/leases/:leaseId/supplemental-rent/:id/client-fiscal-report'), which is a tautology of the title rather than an explanation of purpose. An agent can infer the resource is a client fiscal report tied to a lease and a supplemental-rent record, but nothing explains what that report contains or how it differs from the dozen sibling tools sharing the same supplemental-rent prefix.

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?

The only actionable guidance is a pointer to describe_operation for native request schemas, which is a schema-retrieval instruction rather than a when-to-use rule. There are no conditions for selecting this tool over the many sibling supplemental-rent and fiscal-report endpoints, and no prerequisites or exclusions.

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