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

With no annotations present, the description carries the full burden and does substantial work: it discloses the issuer verifies signature plus identity binding, countersigns, and registers rather than endorses the claim, and it states freshness and length limits. It omits output shape and failure modes, which keeps it from being fully transparent.

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 four terse sentences with no filler: purpose first, then the critical signature prerequisite, then the issuance semantics and constraints, then the private-lane instruction. Every sentence earns its place and the key information is front-loaded.

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 tool with no output schema and no annotations, the description thoroughly covers input validity, preconditions, and protocol meaning, but it never states what the tool returns, what errors an agent should expect, or what happens after the issuer countersigns. That missing response/error behavior leaves an agent unable to fully reason about the call result.

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 already has descriptions for all six parameters, so the baseline is 3; the description adds real value by specifying the ±10 minute ts window, the 200-char claim value cap, and the refusal consequence for missing sig2 on post-quantum identities. It does not add much beyond the schema for meta, sig, and bind, so 4 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 names a specific action ('Relays a provenance request you signed LOCALLY') and a specific resource ('issuer-countersigned provenance'), and makes the lane's role clear by emphasizing the claim is one YOU signed and the issuer countersigns. This sets it apart from sibling null_prov_issuer, which represents the issuer side.

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?

It gives clear context for when to use the tool: with an SDK-built request, on the private lane only, and with explicit preconditions such as a current ts, a post-quantum sig2 when required, and claim values under 200 chars. It does not explicitly name alternatives or state 'use X instead,' so it stops short of a 5.

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