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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that it 'never creates or registers copyright' and mentions legal boundaries, but most of the second sentence is ecosystem boilerplate rather than tool-specific behavior.

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 first sentence is front-loaded and useful, but the second sentence is a long, run-on vendor/ecosystem description that does not help an agent invoke the tool correctly. It hurts conciseness without adding operational value.

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 correctly enumerates what the contract covers (evidence levels, signing roles, timestamp assurance, chain-of-title events, legal boundary). Annotations cover the read-only and closed-world aspects, making the definition fairly complete for a zero-parameter contract reader.

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 tool has zero parameters, so parameter semantics are not applicable. The baseline for zero parameters is 4, and there is no schema content that the description needs to explain.

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 verb ('Read') and resource ('SaSame Provenance & Rights Passport contract') and enumerates the contract's contents. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools like provenance_verify_passport or lookup_passport.

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 gives no guidance on when to use this tool versus alternatives, such as provenance_verify_passport or lookup_passport. It states a read-only nature but not the conditions under which this contract-reading tool is the correct choice.

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