Create order (spends balance)

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

Highlights key behavioral trait 'THIS SPENDS the key's USD balance'. Explains two-step idempotency pattern. No annotations provided, but lacks details on auth or error handling.

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?

Three sentences, front-loaded with purpose and key warning. No filler, efficient and direct.

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?

Explains two-step process, spends balance, required fields. No output schema, but missing return value description is acceptable. Adequate for use.

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 100%, but description adds context: explains confirm as two-step toggle and link as 'target channel/post/bot link', beyond schema descriptions.

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?

Title explicitly states 'spends balance', description specifies 'Stars Cash Flow order' and distinguishes from siblings (cancel, balance, list, status). Clear verb+resource.

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?

Explicit two-step design: call without confirm for estimate, then with confirm=true to place order. No alternatives among siblings, but usage pattern is clear.

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