analyze_volume_profile

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

No annotations are provided, so the description bears full responsibility. It describes what the tool calculates but does not disclose whether it is read-only, any side effects, authentication requirements, or rate limits. The description implicitly suggests it's a query tool, but this is not explicit.

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 short paragraph that front-loads key terms like Volume Profile and VWAP, making it quickly scannable. Every sentence contributes meaningful information without redundancy.

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 covers the purpose and mentions the computational outputs (bands, distributions), but since there is no output schema, it doesn't specify the return format or structure. This leaves some ambiguity for the agent regarding what data to expect.

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 input schema has 67% description coverage, with descriptions for bins, hours, limit, and valueAreaPct. The description adds context for the hours parameter (default 4h, max 24h) and mentions the analysis type, but does not explain tz or pair, which lack schema descriptions. This adds marginal value but does not fully compensate for the missing descriptions.

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 it performs volume profile analysis including VWAP, POC, value area, and calculates bands and distributions. It uses specific financial terms that distinguish it from other technical analysis tools, though it does not explicitly differentiate from sibling tools.

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. It only mentions the hours parameter for specifying time range, but does not indicate when not to use it or suggest other tools for related analyses.

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