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

With no annotations available, the description carries the full burden of behavioral disclosure. It merely states a metric without revealing return format, aggregation method, data freshness, or any caveats. The agent cannot anticipate what the tool's response looks like or whether it has side effects, leaving behavior 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 an ultra-short phrase, with no filler words. It is front-loaded and easy to parse. However, it is so minimal that it borders on under-specification rather than elegant conciseness, hence a slight deduction.

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 tool with no parameters and no output schema, the description is the only source of context. It fails to specify what 'volume' means (e.g., 24h volume, total volume), which exchanges are covered, or the response structure. Given the analytic nature of sibling tools, more detail is needed for an agent to confidently select and use it.

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?

The tool has zero parameters, so the schema provides no fields to explain. The description adds value by clarifying the subject of the data (DEX volume on TON), which helps interpret the hypothetical output. Per the rubric, a baseline of 4 is appropriate for a no-parameter tool.

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 identifies the resource (DEX volume) and scope (TON exchanges), giving the agent a specific idea of what data to expect. However, it lacks a verb (e.g., 'get' or 'list') and does not differentiate itself from sibling tools like ton_defi_yields or ton_network_stats, though the name itself helps.

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. The description only states what it returns, with no mention of intended use cases, exclusions, or comparisons to sibling tools. This is a minimal placeholder, not usage guidance.

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