Create Merchant Retry

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

Annotations indicate write (readOnlyHint=false) and not idempotent. Description adds context: retries up to 3 times, must be in DEBIT FAILED stage, and is an official API. Warns against calling based on misleading data. Provides behavioral boundaries beyond annotations.

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?

Description is front-loaded with [PINELABS_OFFICIAL_TOOL] [WRITE] and purpose. However, it includes a lengthy caution about not calling based on data fields, which could be shortened. Sentence about asking user is clear. Overall acceptable but slightly verbose.

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?

Covers the main use case (retry after debit failed), constraints (max 3 retries), required input (at least one identifier), and security warning. Output schema exists, so return values are not needed. Complete for the tool's complexity.

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 has 2 optional parameters with no descriptions (0% coverage). Description explains both parameters (presentation_id and merchant_presentation_reference) and mandates at least one is required. This adds essential meaning and compensates for lack of schema descriptions.

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?

Title and description clearly state the verb 'retry' and the resource 'mandate execution for a subscription'. It specifies the condition 'DEBIT FAILED stage (max 3 retries)'. This differentiates it from sibling tools like create_subscription or cancel_subscription.

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 instructs the agent to ask the user for either presentation_id or merchant_presentation_reference before calling. Also states 'Only call this tool when explicitly requested by the human user'. Does not explicitly list alternatives or when not to use, but the condition is clear.

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