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

Clearly describes deterministic mathematical checks, no hallucination, and exact return format (PASS/REJECT with reason). With no annotations, the description effectively communicates safety and behavior.

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?

Every sentence serves a purpose: purpose, rules, return, usage requirement, and example. No redundant text; well-structured and front-loaded.

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, input parameters (with example), behavior, return value, and usage mandate. No output schema needed; return description is sufficient.

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 covers all parameters (100% coverage). Description adds a concrete call format example and links parameters to the enforcement rules, enhancing understanding beyond the 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?

States it is a pure-math position risk check that enforces three specific rules and returns PASS/REJECT. Distinguishes from sibling tools like trading_propose by emphasizing it is a pre-trade gate with no AI.

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?

Explicitly states 'Must be called before every trade proposal,' providing clear when-to-use guidance. Does not name sibling alternatives for comparison but implies a sequential workflow.

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