direct-checkout

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

The description details that the call costs 3 MESH, the payment goes directly to the owner's account, and the mesh never holds funds. This provides complete behavioral insight beyond what annotations would offer.

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 extremely concise: two short sentences plus a brief parenthetical. It front-loads the key action and result, with no extraneous words.

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?

Despite having no annotations or output schema, the description fully covers the tool's behavior, security implications, cost, and typical use case. It is complete for the complexity level.

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?

The input schema already provides clear descriptions for parameters (e.g., stripe_key). The description does not add additional meaning beyond what the schema offers, so baseline score of 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 clearly states that the tool accepts a Stripe secret key and returns a hosted payment link. It specifies the core function (owner-direct checkout) and distinguishes itself from other payment methods by emphasizing the mesh never touches the money.

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 indicates the tool is for taking online and QR orders directly, but it does not explicitly mention when not to use it or provide alternatives. However, the context is clear enough for an agent to decide.

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