sigmavue_trade_execute

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

No annotations, but description fully details safety features: fail-closed, kill-switch check before network write, blocked:true response, and simulation mode. Exceeds expectation.

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?

Four sentences, each with a distinct purpose: action, simulation, safety, blocked state. Front-loaded, zero waste.

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 purpose, safety, simulation mode. Output schema exists for return values, so omission of return details is acceptable. Missing parameter format constraints, but overall adequate for execution context.

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%. The description explains the sim parameter fully but leaves symbol, side, quantity, order_type, and requested_price to inference. Adds some value beyond schema.

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 'Place an order — fail-closed', with specific verb and resource. It distinguishes from siblings that list accounts, clients, etc.

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 clear context on using sim=true for demo and fail-closed behavior. Does not explicitly list alternatives or when not to use, but siblings are clearly different operations.

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