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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds one meaningful behavioral detail—that no external-use credit is assigned—but does not disclose other traits like what 'retained' means, authentication needs, or what happens on failure.

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 a single, front-loaded sentence with no filler. It states the action, the target resource, and the key constraint ('without assigning external-use credit') efficiently, making it easy for an agent to parse quickly.

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 simple one-parameter verification tool with read-only annotations, the description is mostly adequate. However, with no output schema, it does not describe what the agent should expect as a return value, and it leaves the distinction from verify_gaip_receipt implicit rather than explicit.

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 description coverage is 0%, so the description must compensate for the undocumented receipt_id parameter. It only implies that receipt_id refers to the terms or delivery receipt being verified, but it does not explain the expected format, where the ID comes from, or any constraints. This is minimal compensation for a single required parameter.

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 ('Verify') and names a concrete resource ('retained Buyer Assurance terms or delivery receipt'), and adds a scope qualifier ('without assigning external-use credit'). It is clear enough to distinguish from most siblings by domain, though the 'or' phrasing is slightly ambiguous and it does not explicitly contrast with similar tools like verify_gaip_receipt.

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: when verifying retained Buyer Assurance terms or delivery receipts without assigning external-use credit. However, it provides no explicit guidance on when not to use it or which sibling alternative to choose, such as verify_gaip_receipt or witness_delivery.

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