fidelity_place_order

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

No annotations exist; description carries full burden. It discloses automatic limit order conversion and auto-calculation of limit_price. Could add more on execution risks or authorization, but current detail is good.

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?

Two concise sentences: first states purpose, second provides critical behavioral notes. No wasted words, front-loaded, easy to parse.

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?

For a 7-parameter tool with required params, description covers order types, dry run, and special-case behaviors. No output schema, so return values are not expected. Adequate for agent decision-making.

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 covers all 7 parameters (100% coverage). Description adds value by explaining dry_run's behavior and automatic limit order logic, which enriches schema definitions.

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 places buy/sell orders for stocks/ETFs on Fidelity, specifying order types (market, limit). It distinguishes from siblings like fidelity_batch_orders (batch) and fidelity_get_quote (quotes).

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?

Provides guidance on using dry_run=true for previewing and automatic limit orders for penny stocks/extended hours. Does not explicitly contrast with batch orders, but context is sufficient for typical use.

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