Create an SMM order (SPENDS MONEY)

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

With no annotations provided, the description carries the full burden. It clearly discloses that this tool spends money, debits the wallet, and that delivery is irreversible once accepted. It also warns about the link being the delivery target. It doesn't mention idempotency behavior or failure modes, but the core risk profile is well covered.

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, all high-value. The most critical warning (spends money, confirm link) is front-loaded, and the irreversible delivery warning is included without padding.

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 money-spending mutation tool with no annotations and no output schema, the description covers the essential risks and constraints. It could mention idempotencyKey usage or what happens on failure, but the core information an agent needs to avoid harmful calls is present.

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 description coverage is 100%, so the schema already documents all five parameters. The description adds context about quantity min/max and the link being the delivery target, but doesn't add much beyond the schema. Baseline 3 is appropriate.

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 states a specific verb ('Buys'), a resource ('social-media service'), and a critical side effect ('debits your wallet'). It also distinguishes itself from siblings like create_order and create_premium_order by naming the SMM service context and the wallet debit.

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 instructs the agent to confirm the link with the user first, warns that delivery cannot be recalled, and states that quantity must be within the service min/max. This is clear when-to-use and when-to-be-cautious guidance, though it doesn't name alternative tools for non-SMM orders.

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