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

With no annotations, the description carries the full burden of disclosing behavior. It transparently states authentication requirements (API key bearer token or paid per-call via Binance/x402), ordering ('newest first'), and what the returned data includes. It also mentions that receipts include seal information 'once sealed', hinting at eventual consistency. This is substantial behavioral disclosure, though it omits details like rate limits or error handling, leaving room for improvement.

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 a single dense sentence that front-loads critical authentication/payment info before the functional description. It packs a list of output fields and optional parameters efficiently, with no superfluous filler. While it is a bit of a run-on, it is appropriately sized for the amount of information and has a logical flow from auth to behavior to parameters.

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?

The tool has an output schema, so return values are structurally defined; the description complements it by listing fields in prose. It covers authentication, payment options, ordering, and optional parameters with defaults. For a moderate-complexity tool, the description is sufficient for an agent to decide whether to call it and how to pass parameters. Minor gaps like parameter units or error semantics are manageable.

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%, so the description must compensate. It explicitly notes that instrument, signalTs, and limit are optional, and specifies limit's default (50) and maximum (500). However, it does not explain the semantics of signalTs (e.g., units, timezone) or instrument values beyond the schema enum. It adds value by stating optionality and limit constraints, but does not fully clarify all parameter meanings.

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 clearly states the tool's purpose: 'Exchange fill receipts of the instrument lane, newest first', and enumerates the fields returned (signal timestamp, venue, side, quantity, price, slippage, order id, seal batch/transaction). This is a specific verb+resource that distinguishes it from siblings like verify_fill (which verifies a single fill) and receipt_spec (a specification).

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 description provides no explicit guidance on when to use this tool versus alternatives, such as verify_fill or instrument_signals. It is implied by the name and the description that this retrieves historical fill receipts, but no when/when-not conditions or alternative tool names are mentioned. The agent must infer usage from the tool name and sibling context.

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