track_confirmation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses the cost ('Costs $0.005 per call'), payment method ('paid in USDC over x402'), and return value ('Returns the merchant's artifact and the payment receipt'). However, it does not elaborate on failure modes, validation requirements, or any side effects beyond generating an ICS invite, leaving some behavioral uncertainty.

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 three sentences, with the core purpose in the first sentence and essential operational details (cost, payment, return) in the following two. Every sentence provides value, there is no fluff, and it is front-loaded with the primary action.

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 moderate complexity (4 params, nested objects, no required params, no output schema), the description gives enough context for an agent to understand its function and when to call it. It clearly states the cost, payment rail, and return value. However, it could be more explicit about the input expectations (e.g., how to provide rawText vs. confirmation) and any prerequisites for using the payment rail, but the schema and overall context make it 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?

The input schema already provides descriptions for all four parameters, so the baseline is 3. The description adds minimal extra parameter semantics, only implying that the 'confirmation' parameter should be the artifact from a booking tool. It does not explain how 'rawText' and 'confirmation' relate or when to use one over the other, but the schema descriptions cover their basic meanings.

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 the tool's function: 'Normalize any merchant confirmation into a portable record plus an ICS calendar invite.' It uses a specific verb ('Normalize') and distinguishes this tool from booking/search siblings by focusing on the post-booking confirmation processing step. The phrase 'any merchant confirmation' conveys broad scope.

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 implies when to use the tool: 'Feed it the artifact any booking tool returned.' This clearly situates it after a booking or purchase flow, differentiating it from the search/booking siblings. It does not explicitly mention when not to use it, but the context is sufficient for an agent to know it's for confirmation normalization rather than discovery or purchasing.

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