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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds valuable tier-based access limits: unauthenticated returns top 3 tickers with minimal fields, free returns top 3 with core fields, Pro returns every tracked ticker with all fields. It doesn't mention rate limits or data freshness beyond 'Today's', so a 4 is appropriate.

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 sentences, front-loaded with the core definition, then use cases, then tier limits. Every clause adds information with no redundant phrasing.

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 zero-parameter, no-output-schema tool whose annotations cover safety, the description covers purpose, usage, and access tiers. It partially describes return fields but leaves 'core fields' and 'all fields' vague, a minor gap that keeps it from a 5.

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 tool has zero parameters, so the schema has no properties to document; the rule sets a baseline of 4 for this case. The description adds no parameter information because there are none to explain.

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?

States a specific verb (rankings of options-flow intent) and resource (tickers showing bullish vs bearish institutional positioning). Expands beyond the title by naming accumulation, distribution, hedging, direction bias, and strength. Does not explicitly distinguish itself from siblings like darkpool_ranking or directional_current, so not a 5.

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 clear example queries ('what are big options traders doing today?', 'where is smart money flowing?') that signal intended use. No when-not-to-use guidance or named alternatives, so not a 5.

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