schwab_orders

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

No annotations provided, so the description carries full burden. It mentions getting orders but does not disclose behavioral traits such as whether it is read-only, rate limits, pagination, or potential side effects. The only added context is that account_hash comes from a specific function.

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 very short and front-loaded: one sentence for purpose and two bullet-style argument descriptions. Every sentence is necessary and there is no redundancy.

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?

Despite having an output schema, the description fails to explain the type of orders returned, ordering, filtering, or pagination behavior. The basic explanation of parameters is not enough for a complete understanding, especially given the many sibling tools.

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 0%, so description must compensate. It provides brief explanations for both parameters: account_hash (source), max_results (default). However, it lacks details like allowed range for max_results, required status, or format of account_hash. This is insufficient for full compensation.

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 orders for a Schwab account,' which is a specific verb-resource pair. It differentiates from siblings like 'schwab_get_order' (singular) and 'open_stock_orders' (likely open only), but does not specify whether orders are all orders or filtered by status.

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 alternatives like 'schwab_get_order', 'open_stock_orders', or 'stock_orders'. No exclusions or prerequisites mentioned beyond needing the account hash.

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