schwab_get_movers

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

No annotations are provided. The description does not disclose behavioral traits such as authentication requirements, rate limits, or any side effects. It simply states the function without additional context about its behavior.

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 concise and front-loaded with the main purpose. The parameter list is presented in a structured docstring format, with each parameter on its own line. It is appropriately sized without wasted words.

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 tool has an output schema, so return values are not needed in the description. However, it lacks context for differentiation among multiple movers tools in the sibling list, and no hints about typical use cases or limitations beyond the index parameter.

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 description adds significant meaning beyond the input schema by enumerating valid index values and providing clear options for sort_order and frequency. This helps the agent understand what values are acceptable, though it does not explain their effects in detail.

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 states 'Get market movers for a given index' with a specific verb and resource. It lists valid index values, making the purpose clear, but does not differentiate from sibling tools like 'top_movers' or 'schwab_get_movers_sp500'.

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?

No guidance on when to use this tool versus other market mover tools. There is no mention of prerequisites, alternatives, or when not to use this tool.

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