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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no mention of auth requirements, response shape, or whether a lease with no sublease returns empty versus error. Sibling-tool ambiguity for accounting lease data is also unexplained.

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 sentence is duplicated verbatim, and the operation-ID sentence is boilerplate. Nothing is front-loaded that helps an agent; the text is short but unstructured and adds zero information density.

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?

For an operation with two undocumented parameters, no output schema, and a very large family of similarly-named lease sub-resource siblings, the description should distinguish this endpoint. It supplies no context beyond the route string.

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% and the description says nothing about the required 'id' or the free-form 'query' object. With two parameters and no schema descriptions, the description carries the burden and fails to provide any meaning.

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 restates the HTTP route verbatim twice ('GET /api/accounting/leases/:id/sublease-profile'). The path implies a read of a lease sublease profile, but nothing states what the resource actually contains or how it differs from the dozens of other lease sub-resource getters.

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?

No when-to-use guidance and no exclusions. The only routing hint is 'describe_operation provides native request schemas', which points to a sibling for schema discovery but not to when this endpoint should be chosen over adjacent lease endpoints like sublease_in_7409936d or liability schedule.

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