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 does disclose the main behavior: aggregating market-wide unusual flow and returning a breadth score, ratio, regime label, and signal counts. However, it omits response shape, date-range handling, and any edge-case behavior, making the transparency only partial.

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, compact sentence that front-loads the output summary and ends with a practical use-case. It contains no filler, though the enumeration of fields is slightly dense.

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?

Without an output schema, the description should clarify the return structure, but it only lists content fields without stating whether the result is a single object or an array of daily rows. The core use case is well covered, but an agent still lacks exact response shape and field-name expectations.

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 description coverage is 100%, with each parameter clearly documented and validated (date, limit, date_from, date_to). The description adds no parameter-specific detail, but the schema fully covers meaning, defaults, and constraints, so the baseline of 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 identifies a specific computation (market-wide breadth of unusual flow per trading day) and lists concrete return fields (score, call/put ratio, regime label, signal counts). It implies differentiation from per-symbol/sector siblings via 'market-wide' and 'overall tone', but does not explicitly name an alternative.

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 gives a direct usage context: answering 'what's the overall tone of the unusual-flow tape?'. This tells an agent when to select this tool, but it does not state when not to use it or mention alternative tools by name.

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