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

Annotations declare readOnlyHint=true and openWorldHint=true, so safety is already covered. The description adds meaningful behavioral context: the default returns a concise summary with CVD and the last 15 trades, while detail:'full' returns the raw trade array, and the 200 limit makes it unsuitable for long periods. This goes beyond basic annotation coverage, though it does not detail exact trade field structure.

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 a single dense paragraph with every sentence serving a purpose: purpose, use cases, distinction from sibling tool, limitation, and output mode defaults. It is front-loaded with the core function and avoids redundant repetition of schema content.

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 lightweight read-only tool with only 3 parameters and no output schema, the description adequately covers purpose, typical use cases, limitations, and both output modes. It does not mention trade ordering or exact timestamp boundaries, but those are minor given the schema and tool simplicity.

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 the schema already fully documents symbol, limit, and detail parameters, including defaults, constraints, and enum meanings. The description adds no new parameter semantics beyond referencing detail:'full' and the 200 limit, which are already present in the schema.

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 begins with a specific verb and resource: 'Trade individual terbaru (aggregate trades), granular per-trade, termasuk sisi buy/sell aggressor.' It clearly distinguishes itself from binance_get_taker_volume_ratio by contrasting per-trade granularity with per-hour aggregation, making its unique purpose evident.

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 explicitly states when to use this tool: to detect absorption ('harga stagnan tapi volume besar searah') or sudden aggression spikes ('lonjakan agresi mendadak'). It also provides exclusions ('bukan untuk periode panjang') due to the 200-limit, and names an alternative tool, giving the agent clear decision guidance.

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