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

Annotations already declare readOnlyHint true, idempotentHint true, and destructiveHint false. The description adds meaningful behavior beyond annotations: it discloses a per-call cost ('Costs $0.001 USDC per call') and specifies byte-identical behavior to a REST endpoint, providing concrete execution expectations without contradicting the annotations.

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 sentences with no filler: the first sentence front-loads the data fields and scope, the second adds cost and endpoint equivalence. Every word contributes useful information, and the structure is immediately scannable.

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 single-parameter, read-only ticker tool with an output schema and rich annotations, the description is complete: it specifies the market, data fields, pair format example, cost, and exact REST equivalence. Nothing critical is missing for an agent to select and invoke the tool correctly.

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%, and the schema describes 'pair' as 'Gate currency_pair, BASE_QUOTE [required]'. The description reinforces this by scoping to 'one Gate currency pair' and providing a concrete example format via the endpoint 'pair=BTC_USDT', which adds clarity beyond the bare schema text.

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 explicitly states the resource ('Gate currency pair'), the specific data returned ('Last, best bid and ask with size, 24h percent change and both base and quote volume'), and the scope ('one Gate currency pair'). This clearly distinguishes it from sibling tools like market_gate_candles, market_gate_depth, and market_gate_trades by enumerating ticker-specific fields.

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 guidance is provided on when to use this tool versus alternatives such as market_kraken_ticker or market_gate_depth. The description covers what the tool returns but does not state selection criteria, exclusions, or mention other tools, leaving the agent to infer usage from the name and field list.

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