schwab_replace_order

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

No annotations provided. The description only restates the operation ('replace/modify') without disclosing behavioral traits like idempotency, side effects, authentication requirements, or error conditions. Does not add value beyond the tool name.

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?

Description is concise (4 lines) and structured as a docstring with parameter descriptions. Front-loaded with purpose, no 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?

Given the existence of an output schema (so return values need not be explained), description covers parameter sources and hints at order_spec structure. However, it lacks error behavior, constraints on modifications, and prerequisites (e.g., order must exist). Moderately complete for a moderately complex tool.

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 has no descriptions (0% coverage). Description adds some meaning for each param: 'account_hash: Account hash from schwab_account_numbers', 'order_id: ID of the order to replace', 'order_spec: New order specification dict (use order builder helpers)'. However, for the nested object order_spec, it only hints at helpers without full structure explanation.

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?

Description clearly states the action ('Replace (modify) an existing Schwab order') with a specific verb and resource. It distinguishes this from sibling tools like schwab_place_order (place new) and schwab_cancel_order (cancel).

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 implies usage for modifying existing orders but lacks explicit guidance on when to use it versus alternatives, such as when not to use it or when to use place/cancel. No exclusions or alternative references.

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