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

Annotations indicate a mutating, non-idempotent operation, and the description adds meaningful behavioral detail: paid items are charged instantly, a welcome allowance exists, shortfalls trigger a deposit suggestion, and 'doge' pays on-chain. This goes beyond the annotations, though the phrase 'you get the shortfall' is somewhat ambiguous about whether the order succeeds or fails.

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 compact and front-loads the core action, then explains payment behavior and alternatives. It is not overly verbose, but the final sentence about 'doge' is slightly disjointed and the shortfall phrasing could be clearer without adding bulk.

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 two-parameter tool with fully documented schema fields, the description covers the essential invocation context: how payment works, what happens on shortfall, and the alternative payment provider. It does not detail return values or explicit failure behavior, but given the low complexity and presence of annotations, the description is reasonably 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?

Schema description coverage is 100%, so the schema already documents both 'slug' and 'provider'. The tool description reinforces that slug comes from the menu and clarifies provider behavior, but it does not add substantive new parameter semantics beyond what the schema already provides.

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 ('Order') and concrete resources ('a drink, look, persona or voice by slug'), making the tool's action unambiguous. It also distinguishes itself from browsing/list siblings like list_drinks, list_looks, and menu by focusing on purchasing/activating a specific slug.

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 gives useful context for when to use this tool: ordering items, with payment handled through the tab or via 'doge' on-chain. It also points to `deposit` as the fallback when the tab is short, and the provider parameter offers an explicit alternative payment path. It does not explicitly enumerate when not to use the tool, but the guidance is clear enough.

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