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 safety behavior is covered by structured data. The description adds no further context — nothing about what COI information contains, pagination, or auth/scope requirements. No contradiction with annotations.

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 same endpoint string is emitted twice back-to-back, wasting half the text, and an opaque operation ID is included with no explanatory value. There is no front-loaded statement of purpose or scope.

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?

There is no output schema, so the description should ideally say something about the COI payload, and it does not. That said, annotations cover the safety profile and the schema fully constrains the required contractId, so an agent can invoke it mechanically — but it cannot predict what comes back.

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 carries the full burden of explaining the contractId path parameter and the free-form query object — and it explains neither. It gives no syntax, format, or filtering guidance for the untyped query object, leaving the agent to infer everything from the route template.

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 identifies a concrete verb and resource (GET a contract's COI information for a given contractId), so an agent can grasp the general purpose. However, it is a near-verbatim restatement of the title/route with the identical string repeated twice, and it never distinguishes this tool from close siblings such as get_leases_by_leaseId_coi_information or get_coi_list.

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 call this versus the many other COI-related or contract sub-resource tools. The only directional hint is the trailing note that describe_operation provides native request schemas, which implies a prerequisite step but does not state when this tool applies versus its siblings.

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