get_options_flow

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

Without annotations, the description carries the burden of behavioral disclosure. It states what the tool returns but does not explain how 'unusual activity' is determined, the time range covered, or any limitations. It does clarify that it identifies potential institutional positioning, adding some interpretive context.

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 reasonably concise and front-loaded with a clear purpose. However, it is somewhat redundant: the Returns section repeats the earlier sentence about volumes/premiums/unusual activity. The structure with Args/Returns is clear.

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?

For a single-parameter, read-only tool, the description is adequate. It covers purpose, usage triggers, and return type. But given no output schema, it could provide more detail on the return structure or define 'unusual activity'.

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 description only adds 'Stock symbol' for the ticker parameter, which is already implied by the parameter name. With 0% schema coverage, this inadequate compensation does not help an agent understand parameter constraints or format.

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 first sentence clearly states the tool's function: analyzing options flow and unusual activity for a ticker. The description further specifies outputs (call/put volumes, premiums, unusual activity) and distinguishes it from sibling tools like get_options_chain by focusing on flow rather than chain 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?

Provides explicit scenarios when to use the tool (options flow, call/put ratio, unusual activity, large trades/sweeps). However, it does not mention alternatives or when not to use it, which prevents a perfect score.

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