toreador_create_session

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

Discloses key behaviors: returns session ID, security code, and payment page URL; session expires after 15 minutes; requires pro plan. No annotations provided, but description adequately covers the mutation nature and constraints.

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?

Two sentences, front-loaded with the main purpose. No wasted words; each sentence provides useful information.

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 4-parameter create tool with no output schema, the description covers return values, expiration, and alternative tool. Lacks details on error scenarios or authentication, but is fairly complete for the task.

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 is 100%, so baseline is 3. Description adds minimal extra meaning beyond the schema: it restates the allowed values for token and chainId but does not elaborate on format or constraints for amount or recipientAddress.

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?

Clearly states the tool creates a hosted payment session for ERC-20 stablecoins on EVM chains, listing specific tokens and chains. It distinguishes from the sibling toreador_generate_qr.

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 when to use this tool (for ERC-20 stablecoins on EVM chains) and when not to (for native tokens or Solana SPL, use toreador_generate_qr). Also notes pro plan requirement.

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