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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds nothing beyond the mention that describe_operation exposes request schemas; it says nothing about pagination, filtering behavior, or what the counterparties payload contains for this openWorld=false, non-destructive read.

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?

Very short and front-loaded, but the first sentence is duplicated verbatim and the Operation ID adds no agent-relevant value, wasting the limited content on redundancy rather than substance.

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 nested-object, zero-coverage, no-output-schema list endpoint, the description should explain how to filter and what is returned. Instead it points vaguely to describe_operation, leaving the definition incomplete for correct invocation.

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?

Two parameters (query, params) with 0% schema description coverage and no descriptions in the schema; the description provides zero parameter meaning, so an agent cannot tell how query filters counterparties or what params accepts. Full compensation is required and absent.

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 restates the tool name and HTTP endpoint twice ("GET /api/counterparties. GET /api/counterparties.") without adding scope, filters, or return info. It is effectively a tautology and does not differentiate from siblings like get_counterparties_by_id_da854dfbb88b182703805889 or get_counterparty_contacts.

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 guidance is a pointer that describe_operation provides native request schemas, which hints at a discovery path but says nothing about when to use this list endpoint versus the many counterparty-related siblings. No when-not or prerequisites stated.

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