schwab_get_movers_sp500

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

With no annotations, the description carries full burden for behavioral disclosure. It describes a read operation ('Get market movers') but does not mention potential side effects, authentication requirements, rate limits, or data recency. The description lacks transparency about what exactly constitutes a 'mover' or any constraints.

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: one sentence stating the tool's purpose, followed by a clear bullet list of parameters. It is front-loaded and avoids unnecessary details. However, the parameter list could be more structured (e.g., using markdown) but remains effective.

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 the presence of an output schema, the description need not explain return values. However, for a simple tool with two optional parameters, it lacks context about the source or update frequency. It adequately covers the parameters but omits practical guidance for interpretation, making it minimally complete.

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 schema coverage is 0% (no descriptions in input schema), so the description must clarify parameters. It lists allowed enum values for 'sort_order' and valid integer options for 'frequency', adding meaning beyond the schema's basic types. However, it does not explain the effect of each sort order or how frequency influences the output, missing an opportunity for deeper clarification.

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 the tool retrieves market movers for the S&P 500 index, using a specific verb and resource. It distinguishes from generic sibling tools like 'schwab_get_movers' or 'top_movers' by explicitly referencing the S&P 500 index ($SPX), though it does not directly compare with the sibling 'top_movers_sp500' which may be identical.

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 is provided on when to use this tool versus alternatives (e.g., for other indices or general movers). There are no usage prerequisites, context, or exclusions mentioned, leaving the agent to infer usage based on the name alone.

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