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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing behavioral beyond pointing at describe_operation for request schemas — no mention of the time window covered by 'history', result volume, or pagination.

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 first two sentences are identical duplicates, wasting half the text. The remaining sentence is a generic pointer to describe_operation that appears on many sibling tools and carries little tool-specific information.

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 and 0% parameter description coverage, the description should explain the shape of an accounting-history response and the accepted query parameters. Instead it only restates the endpoint, leaving a nested-object parameter undocumented and the return value entirely opaque.

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 2 parameters, so the description must compensate and does not. The 'leaseId' path segment is inferable from the URL, but the free-form 'query' object (additionalProperties, unrestricted) is left entirely unexplained — an agent cannot tell what filters or paging keys belong there.

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 repeats the REST path 'GET /api/leases/:leaseId/accounting-history' verbatim twice, which does convey a specific verb and resource (accounting history for a single lease). However, it never explains what 'accounting history' contains, and it does not distinguish this tool from the near-identical sibling get_leases_by_leaseId_accounting_histor_36f63bb15511bf11747bd283. Purpose is identifiable but only at the level of the raw endpoint.

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 prefer this over siblings such as get_accounting_leases_by_id_accounting__* or describe_operation. The only directional hint is 'describe_operation provides native request schemas,' which addresses schema lookup, not tool selection.

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