get_dark_pool_volume_v21

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds value by emphasizing reliance on real data and failure mode, which is beyond annotations.

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?

Three sentences, each serving a distinct purpose: action/sources, outputs, behavior/no synthetic. No wasted words.

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?

No output schema, but description details return values. Adequately covers data fetch tool with low complexity; could mention limits or pagination but not essential.

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 50% (date described in schema, symbol not). Description clarifies symbol context and date format but does not add detail beyond schema. Baseline 3 with minimal compensation.

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?

Clearly specifies action ('Fetch dark pool volume for a symbol'), data sources ('real FINRA ATS reports + Polygon off-exchange trade conditions'), and outputs ('dark pool %, total off-exchange volume, institutional activity score'). Distinguishes from sibling tools by focusing on dark pool data.

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?

States when to use (when real dark pool data needed) and a key constraint ('fails if real sources unavailable'), but does not explicitly mention when not to use or suggest alternative tools among siblings.

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