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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'Offline-compatible' and 'Read-only'. It goes beyond the annotations by scoping the guarantee: it checks signatures, digests and hash chains but 'makes no legal ownership decision', which tells the agent what the result does and does not establish. It stops short of describing the result shape or failure modes.

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 opening sentences are dense and front-loaded with the checks, which is good. However, the trailing GEC/SASAME boilerplate about public-safe discovery, no fabricated demand/revenue and no custody is irrelevant to selecting or invoking this verification tool and dilutes the definition.

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?

With no output schema, the description must carry the burden of explaining what verification returns, and it does not say whether the result is a boolean, a per-check report, or failure reasons. The enumerated checks partially imply the output surface, but an agent cannot predict the response shape from the description alone.

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 single parameter already carries its own description, so the description only needs to add meaning beyond 'passport'. It implies the input is a complete passport object, but adds no structural, format, or validation detail beyond what the schema states. Baseline 3 applies.

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 verb (verify) and resource (a SaSame Provenance & Rights Passport JSON object) and enumerates exactly which assertions are checked (signature, artifact-set digest, event hash chain, signer requirements, timestamp binding). This clearly separates it from siblings like lookup_passport (retrieval) and provenance_passport_spec (specification).

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?

'Offline-compatible' and 'Read-only; makes no legal ownership decision' imply a usage context, but there is no explicit when-to-use guidance and no sibling tool is named as an alternative or complement (e.g., lookup_passport, provenance_passport_spec). Usage must be inferred rather than read.

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