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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable tier-gating behavior: free accounts get top 3, Pro gets up to 200 with all fields. This tells the agent the effective ceiling varies by account, which annotations do not convey.

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 compact sentences, front-loaded with the ranking definition, then the use case, then the tier constraint. Every sentence adds distinct information with no filler.

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 one-parameter, read-only ranking tool with annotations covering safety, this is nearly complete. The description could state the default output count (50) or whether results are limited in fields for free accounts, but the essential behavioral facts (ordering, use case, tier limits) are present.

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%, and the sole parameter (top) is fully documented in the schema with its default of 50 and max of 200. The description's mention of 'top 3' free vs 'up to 200' Pro adds account-tier context but is not per-parameter semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific ranking output ('Tickers ranked by options-flow momentum') and adds the defining dimension ('fastest-changing positioning this session'), which distinguishes it from siblings like directional_current or gex_levels. An agent can identify the resource and its ordering criterion immediately.

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 an explicit example query ('which stocks have the strongest options momentum right now?') that maps natural-language intent to this tool. No exclusions or sibling alternatives are named, but the usage context is clear enough to route correctly among similar flow tools.

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