C2Pa Verify

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

Annotations already cover the safety profile (non-read-only, open-world, non-idempotent, non-destructive), and the description usefully adds the cost model (0.25 USD x402/base/usdc on eip155:8453) and that the call is a remote POST — real value for a budget-aware agent. However, it discloses nothing about what the verification returns on failure, whether payment is required before the call, or what a malformed manifest does, which is the burden a payment-gated tool should carry.

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?

It is short and front-loaded, but its brevity comes from omission rather than compression: two lines consisting of a repeated title and a route/price string. Nothing here is wasted, yet almost nothing is present.

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 explained. But for a paid, open-world verification tool with four undocumented parameters, the description omits the one thing an agent most needs: what C2PA verification actually does and what inputs it expects.

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% across four parameters (manifest, content_hash, expected_creator, expected_generator) and the description supplies no meaning for any of them. Critically, `manifest` has no type declared and is not required, so the description should have said what to pass and in what form — it says nothing.

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?

"C2Pa Verify" merely restates the tool name and title; the only added information is a REST route. It never says what is being verified (a C2PA / Content Credentials manifest against a content hash? a signer identity?), so an agent cannot distinguish it from siblings like v1_data_validate, v1_output_verify, or v1_provenance_verify.

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 when-to-use, when-not-to-use, or alternative-selection guidance at all. The description gives a price and a route but no condition under which an agent should call this instead of the many other verify/provenance siblings.

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