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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'Same body and validation as POST /api/transactions' which hints at API-level validation, but it does not disclose side effects, reversibility, permissions, or output behavior. The behavior beyond the action itself is largely opaque.

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 two sentences, front-loaded with the core purpose and a concise technical note. Every word earns its place, with no redundancy or filler.

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?

Given the tool's complexity (20 parameters, 12 required, no output schema, no annotations), this description is drastically incomplete. It omits details on required fields, expected input formats, validation rules, return values, and any side effects, making it insufficient for an agent to fully understand the tool's behavior.

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 only 10%, and the description adds minimal parameter insight beyond the from/to asset concept already evident in the parameter names. It does not compensate for the lack of schema descriptions for the 20 parameters, leaving many fields unexplained.

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 logs a trade (buy/sell/swap) and specifies the from-asset to to-asset structure, making the primary purpose unambiguous. It is distinguished from sibling tools by explicitly focusing on trades rather than adjustments or reads, though it does not explicitly name alternatives.

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 implies clear usage for logging trades and differentiates from other tools by the trade context. However, it provides no explicit guidance on when not to use this tool (e.g., for balance adjustments) or alternatives, so it lacks explicit exclusions.

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