justhandled_proof_to_channel_evidence_packet

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. The only behavioral trait disclosed is the $0.25 USDC cost on Base mainnet. It does not explain whether the operation writes to chain, what the output packet contains, what happens on failure, or any authorization requirements.

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 two sentences, front-loaded with purpose and ending with a key cost qualifier. Every sentence contributes useful information without fluff or repetition.

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?

The tool has a complex 8-parameter nested schema and no output schema, yet the description is minimal. It lacks expected return value/output format, usage examples, and sibling differentiation. The cost disclosure is helpful but insufficient for an agent to confidently invoke this complex tool.

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. It does map several key concepts (claims, observed proof, channel rules, required artifacts, link treatment, attribution, pricing disclosure, human-authored identity fields) to the input groups, adding meaningful context. However, it omits explanation for parameters like observed_at and max_evidence_age_days and leaves structural details to the schema.

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 action: 'Map product claims and observed proof to current channel rules, required artifacts, link treatment, attribution, pricing disclosure, and human-authored identity fields.' This clearly distinguishes it from sibling tools by focusing on product-claim-to-channel evidence. The verb 'Map' is somewhat abstract, but the resource and purpose are evident.

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 a use case—mapping claims and evidence against channel rules—but provides no explicit when-to-use guidance, prerequisites, or exclusions. It does not mention alternatives among sibling tools. The cost note is contextual but not actionable usage guidance.

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