pause_trading

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

With no annotations, the description carries the full burden and does well: it discloses exactly what stops working (fills, trigger arming, trigger firing), that stopping is immediate and always safe, and that no confirmation is required. It omits permission requirements, whether open orders/positions are cancelled, and how the state is later reversed.

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?

Front-loaded with 'KILL SWITCH', then the exact effect, then the no-confirmation guarantee, then trigger phrases. Every sentence is actionable and nothing is wasted.

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 one-parameter emergency stop with no output schema and no annotations, the description covers the essential behavior and urgency. Minor gaps remain around auth, side effects on open positions, and reversal, which are left implicit via the resume_trading sibling.

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% and the description never mentions trader_id. However, with a single self-evident parameter (whose trading to pause) and the schema marking it required, the ambiguity cost is low, leaving this adequate but with a clear documentation gap.

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?

Names a specific action (stops) with precise scope: fills, trigger arming, and trigger firing all fail while paused. An agent can distinguish this from the sibling resume_trading without opening any schema.

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?

Gives clear triggering context ('Call the moment anything looks wrong') and user phrasings ('stop everything' / 'pause trading'), plus the reassurance that no confirmation is needed. It does not explicitly name resume_trading as the counterpart, so the routing is implied rather than stated.

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