volume_24h

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

The description discloses that the tool is a paid call costing $0.001 via x402, which is a key behavioral trait beyond the schema. However, it does not mention whether the operation is read-only, what happens if the ticker or venue is invalid, or any rate limits. With no annotations, this partial disclosure is adequate but not comprehensive.

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 wasted words. The purpose is front-loaded, and the cost is appended efficiently. Every sentence serves a purpose.

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-parameter tool with no output schema, the description explains what it does but omits what the response looks like (e.g., return type, structure). This might force the agent to guess or rely on error handling. The cost note is useful context.

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% with simple descriptions ('Venue', 'Ticker'). The description adds no extra meaning beyond restating 'for a ticker on a venue'. The agent receives no hints about format, examples, or allowed values, so the description adds minimal value over 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 clearly states that the tool provides the 24-hour perpetual volume for a specific ticker on a specific venue. The verb 'get' is implied, and the resource and scope are well-defined. It differentiates from siblings like funding_arb and volume_anomalies by focusing on raw volume, but it does not explicitly contrast them.

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 does not provide any guidance on when to use this tool versus alternatives like open_interest or funding_screener. There is no mention of prerequisites, limitations, or typical use cases, leaving the agent to infer usage from the name alone.

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