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

Annotations already declare readOnly, idempotent, and closed-world, yet the description adds substantive trust-model caveats: digest-only handling of witness payloads, no outbound request or payment, and that caller keys do not establish issuer identity and a signature grants no authority. These go beyond the annotations, though 'Digest-only for witness payloads' is terse and leaves the actual constraint ambiguous.

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?

Four compact sentences with no filler, and the core action is front-loaded. It is dense to the point of being cryptic in places, but every sentence carries distinct information.

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 four required nested-object parameters, no output schema, and no parameter documentation, the description covers the operation and trust model but omits parameter formats and says nothing about the result shape (a verified/not-verified outcome, error handling). An agent could call it but would be guessing on argument construction.

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 required parameters, three of which are untyped nested objects (jwks, response, verification). The description only loosely gestures at 'JWKS' and 'expected values' and says nothing about what belongs in 'response' or the 'verification' object, so it does not compensate for the coverage gap.

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?

States a specific verb and resource ('Verify a time or witness receipt') and names the inputs (caller-trusted JWKS, expected values). It does not differentiate from the sibling popcorn_verify_v2, which is the obvious ambiguity for an agent picking a tool.

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 phrase 'using caller-trusted JWKS and expected values' implies the context (caller-side verification against known keys) and 'No outbound request or payment' rules out a class of alternatives. However, there is no explicit when-to-use/when-not guidance and no reference to popcorn_verify_v2, popcorn_time, or popcorn_witness.

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