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. The description adds only that 'describe_operation provides native request schemas', which is a useful discovery hint but discloses nothing about response shape, size, or scope of the summary.

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 single substantive sentence is duplicated verbatim, doubling length without adding information, and there is no front-loaded explanation of the operation's purpose. Little of the text earns its place.

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 0% schema description coverage, a nested object parameter, and no output schema, the description should explain what 'sublease income summary' returns and how the lease id is supplied. It instead defers entirely to describe_operation, leaving an agent unable to predict the result.

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 parameters (a required nested 'params.id' and an untyped 'query' bag), and the description supplies no meaning for either. The only compensating value is the pointer to describe_operation as the place to find the native request schema.

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 only repeats the raw route 'GET /api/accounting/leases/:id/sublease-income-summary' (twice) with no plain-language explanation of what the sublease income summary contains or represents. The resource is at least identifiable from the path, but it is essentially a restatement of the tool name rather than a stated purpose.

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, no prerequisites, and no differentiation from the many close siblings such as get_accounting_leases_by_id_sublease_pr_897d0325fc351933c23e4160 or the other leases-by-id sub-resource tools. The only pointer is to describe_operation for schemas, which is not usage guidance.

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