get_market_movers

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

With no annotations, description carries full burden. It discloses it returns up to 100 stocks with price, volume, and percentage change, and indicates real-time/recent sessions. No mention of auth needs or rate limits, but adequate for a read tool.

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?

Four sentences, each with clear purpose: function, usage, filtering, output. No redundant information. Front-loaded with purpose and usage.

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, description covers return data (price, volume, percentage change). Parameter count is low and explained via schema and description. Slightly lacking in full parameter detail but sufficient for agent use.

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 coverage is 0%, but description adds value by explaining filtering by market session and categories implicitly. The schema itself provides enums and descriptions, but the tool description does not describe the input_data structure directly, relying on the schema.

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?

Clearly states the tool identifies top gainers, losers, and most active securities by volume. Provides specific synonyms like 'what's hot' and 'what's moving', distinguishing it from sibling tools that retrieve other 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?

Explicitly lists usage scenarios, including phrases like 'what's hot', 'market leaders', and 'pre-market activity'. Supports filtering by market session but doesn't mention when not to use, though context is clear.

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