get_volume_profile

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

No annotations are provided, so the description bears the full burden of disclosing behavioral traits. It does not explicitly state that the tool is read-only, nor does it mention auth requirements, rate limits, or error behavior. The interpretive content is useful but does not cover operational behavior.

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 two-paragraph structure is efficient: the first sentence is a crisp summary, and the second paragraph adds genuinely useful trading context. It is slightly wordy but every sentence earns its place.

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?

An output schema exists, so explaining return values is unnecessary. The description covers the core concepts and their trading significance, making the tool's purpose and output clear. Minor gaps like data source or refresh rate do not materially impair completeness.

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 descriptive parameter details (e.g., 'higher is a finer profile' for buckets). The tool description does not add parameter-level semantics beyond the schema, so the baseline 3 applies.

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 'Volume-by-price for a symbol' and lists specific outputs (point of control, value area, high/low volume nodes). It distinguishes itself from price and oscillator tools via the auction-theory framing, but does not explicitly name sibling tools, so it falls short of a 5.

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 phrase 'Answers ... the auction-theory reading that price and oscillators cannot give' implies when to use this tool: when volume-based market structure is needed. It provides clear context but stops short of explicit alternatives or exclusions, so it earns a 4.

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