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

With no annotations, the description carries the full burden and delivers meaningful behavioral facts: tamper-evidence semantics, what the receipt does and does not attest, an explicit 'do not send raw payloads or secrets' constraint, and per-call cost ($0.001 USDC). It stops short of stating auth requirements or whether verify/status are read-only, but the safety-relevant disclosure is strong for an un-annotated tool.

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 first three sentences are tight and correctly front-loaded, but roughly two-thirds of the text is cross-tool routing boilerplate, including a sentence enumerating what Agent Action Gate does NOT do that has nothing to do with this tool. That bulk does not earn its place in this definition and dilutes the tool-specific content.

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?

An output schema exists, so return values need not be described, and the 100%-covered input schema handles parameters. The description covers purpose, trust semantics, security constraint, and price, leaving only auth/permission requirements and read-vs-write status for verify/status unstated. Adequate for an un-annotated mutation-or-read tool of this 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 description coverage is 100% and the oneOf branches fully constrain the issue/verify/status operations, so the schema does the heavy lifting. The description adds only the 'do not send raw payloads or secrets' constraint and implies the create/verify split; it does not explain the meaning of action_id, result_hash, external_reference, or scope beyond what the schema encodes. Baseline 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 states a specific verb and resource — 'Create or verify a tamper-evident receipt of an agent-reported outcome' — and adds a trust-boundary caveat ('proves DropEngine recorded a claim, not that the external event independently occurred') that helps distinguish it from verification-style siblings. It is clear, though it never explicitly names the siblings it differs from (verify_claim, action_lock).

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 routing paragraph gives when-to-use guidance across the family ('known single capability → call the direct tool', 'multi-step objective → read the matching workflow recipe'), which implies this is a direct capability tool. However, none of it is tool-specific: it never says when to issue vs. verify vs. status, or when to prefer a receipt over verify_claim. Guidance is implied rather than stated for this tool.

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