verify_conversion_delivery

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose a meaningful behavior—returning unknown when no explicit receipt is available—but it does not clarify possible classifications, error behavior, or whether any side effects occur.

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 entire description is one efficient, front-loaded sentence. It communicates the operation, the input condition, and the fallback result with no wasted 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?

There is no output schema, so the description should specify what classification values or return shapes the agent can expect. It only mentions the 'unknown' fallback, leaving the main delivery classifications and any error conditions undescribed.

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 schema has one undocumented nested object parameter, providerReceipt, and schema description coverage is 0%. The description only hints at it via 'explicit receipt' without explaining the required shape or fields, leaving the agent to guess what a valid receipt must contain.

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 uses a specific verb ('Classify') and a specific resource ('provider delivery'), and it identifies the input source as an explicit receipt. The fallback 'or return unknown' adds scope, though it does not explicitly contrast with sibling tools like check_conversion_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?

There is no guidance on when to prefer this tool over alternatives such as check_conversion_status or verify_capture. The phrase 'from an explicit receipt' implies a precondition, but no explicit when-to-use or when-not-to-use information is provided.

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