schwab_get_open_stock_orders

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

No annotations are provided, so the description must carry full behavioral disclosure. It only states 'get open equity orders' with no mention of authorization needs, rate limits, pagination, or what constitutes 'cancellable'. This is essentially no behavioral transparency.

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 concise, with two short sentences and parameter explanations. It is efficient and front-loaded. However, the parameter explanations are in a function-arg style that could be more structured.

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 output schema exists, return values need not be explained. However, the description lacks details on how results are ordered, what 'cancellable' means, and how to distinguish this from similar tools. For a tool with only two parameters, it is somewhat complete but missing important context for proper usage.

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%, so the description must add meaning. It explains account_hash comes from 'schwab_account_numbers' and max_results is a limit 'before filtering', which adds some context. However, it doesn't explain the filtering process or that max_results defaults to 200. Adequate but not comprehensive.

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 it retrieves open (cancellable) equity orders for a Schwab account, specifying 'open' and 'cancellable' to distinguish from general orders. However, it lacks explicit differentiation from siblings like 'open_stock_orders' and 'schwab_orders', which have similar names.

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?

The description provides no guidance on when to use this tool versus alternatives like 'open_stock_orders' or 'schwab_orders'. There are no exclusions or context for usage, leaving the agent to infer from the name alone.

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