calculate_margin

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

No annotations exist, so description carries full burden. It discloses approval requirement, demo-only restriction, and that the order is not actually sent. This is clear for a calculation tool, though no mention of rate limits or error conditions.

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?

Description is two sentences, direct and efficient. It hits the key points without extraneous text, though a more structured format (e.g., listing constraints) could improve readability.

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?

Given 4 required parameters and no output schema, the description covers the tool's purpose and constraints but lacks parameter elaboration, leaving the agent with gaps in understanding how to correctly fill inputs.

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% (no descriptions in schema) and the description does not explain any parameter meaning beyond their names. The agent must infer from parameter names like 'price', 'symbol', 'volume', 'order_type', which is ambiguous without further clarification.

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?

Description clearly states 'Calculate required margin for a hypothetical order' with a specific verb and resource, and the context of margin calculation distinguishes it from sibling tools like calculate_profit or check_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?

Provides explicit constraints: 'Requires approval; demo accounts only; never sent.' This tells the agent when to use (demo accounts) and important behavioral notes, though it doesn't explicitly list alternatives among siblings.

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