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

The description presents this as a read-only listing operation ('List trades'), yet annotations declare readOnlyHint=false, an explicit conflict about whether the call can mutate state. The only additional context the description supplies is the Authorization: Bearer header requirement, which does not offset the contradiction.

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?

Two short sentences, purpose front-loaded, no filler. The auth-requirement sentence is terse and actionable, though it sits a bit awkwardly next to the contradiction with the read-only annotation.

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?

For a simple two-optional-parameter list tool with no output schema, the description covers scope and auth but omits any explanation of filtering (status values), result size (limit semantics, pagination), and ordering. Minimum viable, with clear 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 description coverage is 0% and neither 'limit' nor 'status' is mentioned in the description. 'status' is a free-form string with no enum and no documented valid values, so the description does nothing to compensate for the coverage gap; only the schema's own maximum/minimum on 'limit' carries meaning.

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?

States a specific verb ('List') and resource ('trades') and narrows scope to 'where your bot is buyer or seller', which is more informative than the bare tool name. It does not explicitly contrast itself with related siblings such as get_delivery or open_trade, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The scope phrase implies 'use this to see your bot's trade history', but an agent must infer that from the name and sentence alone.

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