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

With no annotations, the description carries the behavioral disclosure burden and does so reasonably: it specifies the metrics returned, the sector-label universe (11 GICS sectors plus Diversified, Unknown, and Unclassified), and the 'only labels with activity, at most 14 rows' constraint. It does not mention ordering, response container format, or units, but these are secondary for a read-only rollup.

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 one front-loaded sentence that leads with the core question and packs necessary details into a parenthetical without filler. It repeats nothing from the schema and every phrase adds useful information.

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?

Given no output schema and no annotations, the description compensates well by listing the returned metrics and row-count constraints, while the schema covers the two optional parameters. It stops short of specifying the exact response object shape and sort order, but an agent can invoke the tool correctly from this definition.

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 both parameters (date and limit) documented including defaults and bounds. The tool description adds no parameter-level meaning beyond what the schema already provides, 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 identifies the tool as a sector-level rollup of the day's unusual options premium and enumerates the returned metrics: total premium, volume, average net delta, and bullish/bearish counts. The sector-label scope distinguishes it from siblings like get_symbol_flow, though it lacks an explicit verb such as 'returns' or 'lists'.

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 conveys the usage context—sector concentration of daily unusual options premium—but does not explicitly say when to choose this tool over get_symbol_flow, get_expiry_concentration, or other siblings. No alternatives or exclusions are mentioned, so guidance is only implied by the sector-grouping language.

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