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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered elsewhere. The description adds nothing on top of that – no pagination behavior, no default result limit, no note about what scope of certificates (entity/workspace) is returned.

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 endpoint string is duplicated verbatim, which wastes half the text. The remaining sentences (operation ID, describe_operation pointer) are procedural metadata rather than useful information for an agent already reading the tool definition.

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?

No output schema, no parameter documentation, and a free-form query object mean the description carries the full explanatory burden – and it delivers none of it. An agent cannot determine what this returns or how to constrain the call without chaining into describe_operation first.

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 both parameters ('query', an unconstrained free-form object, and an empty 'params') are opaque. The description never clarifies what belongs in 'query' or how it maps to the native request schema; the pointer to describe_operation is the only crumb, and it defers rather than explains.

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 is the raw endpoint restated twice ('GET /api/insurance/certificates'), which is essentially tautological with the tool name and title. It does convey that this is an unfiltered GET over insurance certificates, but it says nothing about what a certificate record contains or how this differs from nearby siblings like get_insurance_policies 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 statement of when to use this tool versus get_insurance_policies, get_coi_list, or the generic execute_read. The only routing hint is 'describe_operation provides native request schemas', which tells the agent how to get a schema, not when this operation is the right choice.

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