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

No annotations are present, so the description carries the burden. It discloses a pay-per-call requirement (one cent over x402), the unpaid response behavior (returns price and how to pay), and a data-availability limitation (history starts when record-keeping began). This is useful, but it doesn't clarify read-only nature, return format, or side effects, leaving gaps.

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 description is relatively short but stylistically ornate ('how one agent's record has moved' and 'a record we keep, not one the chain gives away'). It front-loads a vague metaphor rather than a direct purpose, and the payment details are embedded mid-description rather than clearly separated. Efficient in length but not optimally structured.

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?

With no annotations and no output schema, the description must compensate. It mentions payment behavior and data scope, but it omits what the tool returns (e.g., fields, format), prerequisites beyond payment, and how the parameters shape results. For a two-parameter tool, this leaves agents uncertain about successful invocation and interpretation of results.

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 exactly 50%: 'days' is described (1 to 365, default 90), but 'address' has no schema description. The tool description adds no meaning for either parameter—it doesn't clarify what 'address' refers to or how 'days' interacts with the history. Given the moderate coverage and no compensatory description, the score is low.

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 hints that the tool shows how an agent's record has moved (dealings, payers, concentration, delivery) over days, which aligns with the name 'history'. However, it lacks a crisp verb+resource statement and does not explicitly differentiate from sibling tools like counterparty_check or counterparty_bulk, leaving the purpose somewhat inferential.

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?

No guidance is given on when to use this tool vs. the listed siblings (counterparty_bulk, counterparty_check, find_agents, preflight_payment). The description only mentions payment mechanics, not selection criteria or alternatives.

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