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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of what COI payload is returned, whether the document must exist, or any error/permission behavior for a read that is scoped to both a lease and a document.

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 meaningful line is duplicated verbatim, which is pure waste, and the remaining content is a machine ID plus a pointer to another tool. Nothing is front-loaded in human-readable terms about what the call returns.

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 a read-only, annotated, parameterless-output endpoint the bar is modest, and the path does encode the resource hierarchy (lease → document → counterparty COI). Still, with 0% schema coverage and no output schema, an agent gets no information about the response shape or the meaning of the document-scoped COI, leaving a real gap.

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 must compensate but does not. The path template implies 'id' is a lease ID and 'documentId' a document ID, but there is no clarification of formats, whether these are UUIDs or external IDs, or how the optional 'query' object is used.

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 URL path verbatim twice, which is essentially a restatement of the tool name/title rather than an explanation. 'counterparty-coi' implies a certificate-of-insurance document scoped to a lease, but the description never says so in plain language or distinguishes this from the many sibling lease-document endpoints.

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 alternatives named. The only pointer is 'describe_operation provides native request schemas', which is a schema-lookup hint, not usage context — and it defers the caller to another tool rather than explaining when this endpoint is appropriate versus e.g. get_leases_by_leaseId_documents_by_docu_*.

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