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

With no annotations, the description carries the full burden. It discloses that the data is 'live', 'non-custodial', and 'free, no key, no custody', which conveys safety, cost, and authentication behavior beyond the schema. It also outlines the row contents. It does not mention result ordering or response envelope details, but the most decision-relevant behaviors are covered.

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?

Four sentences with each earning its place: value proposition, row contents, use cases, and safety/auth. The core purpose is front-loaded and there is no filler or repetition of schema details.

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?

There is no output schema, so the description compensates by enumerating the row fields (strategy hash, network, pair, tokens, settled volume) and giving usage scenarios. It does not specify the exact response container, ordering, or default network behavior, but for a simple filterable list tool these gaps are minor.

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 100%, so all three parameters are already well documented. The description adds only 'Filter by network and by pair,' which mirrors the schema rather than adding new meaning. Per the calibration rule, this is a baseline 3.

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 identifies the resource (live USDC/USDT maker positions), what they are (non-custodial stablecoin liquidity an agent can trade against), and what each row contains. It implicitly differentiates itself from siblings like trdefi_position_detail by presenting this as the multi-row survey/list tool rather than a single-position detail view.

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?

Gives explicit when-to-use context: 'Use this before a stablecoin swap to find a real on-chain counterparty, or to survey where stablecoin liquidity sits.' It also mentions the available filters, but it does not explicitly name alternative sibling tools or state when not to use it, so it stops short of a 5.

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