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 without the description. The description adds nothing beyond that: no statement of what the endpoint returns, whether it 404s for missing leases, or any auth/tenancy requirements.

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?

It is short, but the one substantive sentence is duplicated verbatim, and the operation ID hash is noise for an agent. Nothing is front-loaded about what the call actually yields.

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 a nested free-form query parameter, the description needs to carry the burden of explaining the payload and filter surface, and it does not. Given the annotations cover safety, the missing pieces are purpose, return shape, and query semantics — all essential here.

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 two parameters. It does not explain that leaseId is a required path identifier, nor what the free-form 'query' object (additionalProperties: {}) accepts — a significant gap for an open-ended query bag with no enum or property hints.

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 route 'GET /api/leases/:leaseId/coi-information' twice, which is a tautology of the name and title. It never says in plain language what COI (certificate of insurance) information is returned or how that differs from the many sibling COI/insurance tools such as get_coi_list or get_insurance_certificates.

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 when-to-use guidance and no mention of alternatives among the 400+ siblings, including the closely related get_contracts_by_contractId_coi_informa_66286e62d8b284210948cf58. The only actionable pointer is that describe_operation supplies native request schemas, which is a schema lookup hint rather than usage guidance.

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