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

With no annotations, the description carries the full disclosure burden and largely drops it: it doesn't state that a bearerToken may be needed for auth, whether the call is read-only (only implied by 'Get'), what pagination defaults or ordering look like, or anything about rate limits. 'Paginated' is the sole behavioral hint.

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?

Two short sentences, front-loaded with the action and resource, with zero filler. It is efficient, though the brevity is closer to under-specification than disciplined concision.

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?

A four-parameter tool with an auth parameter, no annotations, no output schema, and only 50% schema coverage needs a description that fills gaps around auth, pagination behavior, and return shape. The description addresses none of these, leaving the agent to guess.

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 50%, with merchant and bearerToken described in the schema. The description adds only 'Paginated', which loosely maps to page/limit but gives no meaning for the numeric parameters, and says nothing about merchant identification beyond the schema's 'Merchant pubkey'.

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 states a specific verb and resource ('Get payment history for a merchant'), which is enough to distinguish it from siblings like create_payment_link or get_usdc_balance. It stops short of naming a sibling or scoping the resource further, so it lands at a clear-but-undifferentiated 4.

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 indication of when to use this tool versus alternatives such as get_payment_link or list_products, and no prerequisites are stated. The only usage cue is 'Paginated', which hints at iterative calls but is not framed as guidance.

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