analyze_volume_profile

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

No annotations are provided, so the description carries the full burden. It lists what the tool calculates but does not disclose whether it is read-only, any side effects, potential limitations (e.g., data availability), or the response structure. This is insufficient for a tool with zero annotation coverage.

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 concise sentence with a clear prefix and all core information front-loaded. It avoids verbosity and directly communicates the purpose and key parameter.

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?

The description lists the computed metrics (VWAP bands, volume distribution, trade size distribution), which gives some sense of output. However, since there is no output schema, it lacks details on the output format or structure, and it omits operational constraints like supported pairs or data freshness. It is adequate but not complete for a tool performing multiple calculations.

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 67%, and the description only adds a note about 'hours' (default 4h, max 24h) which is already in the schema. It fails to explain the important semantic that 'hours' overrides 'limit' when both are provided, leaving agents to discover this only through the schema. This is a meaningful gap.

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 the tool performs volume profile analysis and lists specific outputs (VWAP±σ bands, volume by price, trade size distribution). It is distinct from sibling tools by focusing on volume profile, but it doesn't explicitly contrast with similar analysis tools like analyze_indicators.

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 mentions the 'hours' parameter for period specification but gives no guidance on when to use this tool versus alternatives such as analyze_indicators or get_flow_metrics. There are no exclusions, prerequisites, or when-not scenarios provided.

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