place_stop_order

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

No annotations provided, so description must disclose behavior. It explains the trigger condition and mentions default time validity. However, lacks details on post-trigger behavior (e.g., becomes market order), potential slippage, or execution guarantees. Adequate but not thorough.

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?

Efficient one-sentence summary followed by structured parameter list and return type. No redundant information. Every sentence adds value.

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?

Covers all parameters, return type, and core behavior. Missing context on order lifecycle (e.g., how stop order executes after trigger) and potential risks. With no output schema and no annotations, it's reasonably complete but could include an example or edge case note.

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 description must explain parameters. It lists all four arguments with clear explanations: ticker with example, quantity as number of shares/units, stop_price as trigger point, time_validity with default and enum values. Adds substantial meaning beyond schema types.

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?

Clearly states it places a stop order triggered by a specified stop price. Verb 'place' and resource 'stop order' are explicit. Distinguishes from sibling order types like limit, market, stop-limit by specifying the stop condition.

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 vs alternative order types (limit, market, stop-limit) or other trading tools. Agent has to infer from name and description alone.

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