usdc_get_deferred_trade

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns status and funding steps, but it does not explain authentication needs despite schema fields for apiKey, accountRef, and sessionPrivateKey.

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 single sentence is front-loaded and contains no wasted words. It is appropriately compact for a status lookup, though the terseness contributes to the missing sibling and return-value context.

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?

It identifies the input key and mentions output themes, status and funding steps, but there is no output schema and the description does not explain what those funding steps are or how this differs from related trade-status tools. It is minimally adequate but leaves meaningful gaps.

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 100%, so all five parameters are documented in the schema itself. The description only reinforces that tradeId identifies the deferred trade and adds no meaning beyond the schema for the authentication-related parameters.

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 verb and resource: retrieving status and funding steps for a deferred USDC trade by tradeId. It does not explicitly distinguish this from closely named siblings such as usdc_wait_for_trade, usdc_get_pending_trades, or usdc_get_funding_status.

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?

It gives no guidance on when to use this tool versus alternatives. An agent must infer that this is for checking a known deferred tradeId, but the description never says so or when not to use it.

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