Place spot order

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

No annotations are provided, so the description carries full burden. It discloses the paper nature, required scope ('trade:spot'), and that it's not financial advice. However, it lacks specifics on success/failure behavior or response format.

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?

The description is four sentences, front-loading the core purpose and essential constraints. Every sentence adds unique value without repetition or fluff.

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 6-parameter tool with no output schema, the description covers constraints, required scopes, user confirmation, and paper trading context. It is missing explicit error handling or response details, but is still fairly complete.

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?

With 67% schema coverage, the description adds critical information: clarifies coinId is a UCID (not ticker), states when limitPrice and stopPrice are required, and explains orderType enum values. This goes well beyond the schema alone.

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 starts with a clear verb+resource: 'Place a paper spot order.' It specifies coinId as a UCID (not ticker), lists orderTypes, and clarifies it's paper trading with virtual funds. This distinguishes it from siblings like spot_quote or cancel_spot_order.

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 explicitly states 'CONFIRM with the user before calling' and 'Paper trading only — virtual funds (50,000 mUSD).' While it doesn't directly compare to sibling tools like spot_quote for quotes, it provides clear context for safe usage.

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