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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered structurally. The description adds essentially nothing beyond restating the HTTP verb: no note on pagination, filtering semantics, or what the list contains. It does not contradict the annotations, but it fails to add value beyond them.

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 sentence 'GET /api/coi-list.' is duplicated verbatim, which is pure waste, and the operation ID adds no agent-facing meaning. The remaining information is front-loaded but thin.

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 list endpoint with two undocumented free-form parameters, no output schema, and numerous COI-related siblings, the description provides no resource identity, no filtering semantics, and no return-shape hints. An agent cannot confidently invoke it or tell it apart from alternatives.

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 coverage is 0% and the two parameters are an untyped free-form 'query' object and an empty 'params' object, so the schema gives no help. The description only says describe_operation provides the native request schema, which points elsewhere rather than explaining what query keys are accepted or how filtering works.

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 merely repeats the endpoint path 'GET /api/coi-list' twice and adds an opaque operation ID. It never says what a 'coi-list' actually is (certificates of insurance) or what entity scope it returns, so an agent cannot distinguish it from siblings like get_contracts_by_contractId_coi_information or get_leases_by_leaseId_coi_information. It is effectively a tautology of the title.

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?

The only actionable hint is the pointer to describe_operation for request schemas, which is a meta-instruction rather than guidance on when to choose this tool over the many COI-related siblings. No conditions for use, prerequisites, or exclusions are stated.

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