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

This goes beyond simple status flags. It clarifies critical flow details by stating 'No charge, Stripe session or video generation happens here' and instructs the agent exactly how to handle the payment link and what to do upon failure.

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 dense but highly efficient, front-loading the core action before detailing constraints, operational boundaries, and financial mechanics, all in one coherent block.

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 the tool's complexity—being an intermediate, non-destructive transactional step—the description covers the required lifecycle, payment mechanics, and failure conditions, making it maximally complete for the agent's 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?

Since schema coverage is 0%, the description must carry the entire burden. It defines constraints on characters (1–2, without photos), the payment structure (pricing based on offer), and the nature of the lyrics input.

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 starts with a direct and specific goal: 'Create an UNPAID order for 1–2 original characters, without photos.' This is clear and immediately distinguishable from sibling tools like `get_order_status`.

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?

It provides explicit prerequisites for use: 'ONLY call after the user explicitly approves the characters, four lyrics and delivery email.' It also guides behavior by stating, 'Do not automatically retry an uncertain order call.'

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