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

With no annotations, the description carries the behavioral burden. It does disclose that results are ranked by estimated premium and that this matches the view used in alert emails. However, it does not state read-only behavior, data freshness, or whether results are sorted descending, leaving some behavioral details to inference.

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?

Two tight sentences: the first defines what the tool returns and how it ranks, the second gives a representative user question. No filler or repetition, and the core scoping is front-loaded.

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?

The combination of a focused description and a well-described schema is mostly sufficient for a read-only listing tool. The main gaps are the lack of explicit descending-sort confirmation and an output schema or return-structure note, but these are minor for this tool type.

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 83%, so the baseline is 3. The description adds no parameter-specific meaning beyond the general 'estimated premium' ranking concept; it does not clarify the undocumented 'type' parameter or enrich any of the schema-described parameters.

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 returning the day's biggest options bets ranked by estimated premium, with an explicit user query example. It is specific about the resource and ranking metric, and the phrase 'largest options trades today' distinguishes it from flow-history or sentiment siblings, though it does not name a sibling explicitly.

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?

It provides a concrete use case: 'Perfect for what were the largest options trades today?' This tells the agent the intended query context. It does not mention alternatives, exclusions, or when not to use this tool, but the context is clear enough for selection among siblings.

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