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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Read' matches this safe profile. It adds 'signed receipt-backed' provenance context, but does not explain verification behavior or response semantics. With annotations covering safety, the description is adequate but not rich.

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 a single, compact sentence with no filler. The action verb is front-loaded, and every word contributes to identifying the resource.

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 no-parameter read tool, the description and annotations cover the core needs: safety, action, and target resource. However, with no output schema and no explanation of what the manifest contains or how 'signed receipt-backed' affects the result, an agent may still have uncertainty about the tool's output.

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 accepts zero parameters and the schema is 100% covered, so there are no parameter details the description must clarify. A baseline of 4 is appropriate since parameter documentation is not a burden here.

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 clearly identifies the action ('Read') and the resource ('signed receipt-backed Wever Commerce Index manifest'), giving it a specific object. However, it does not distinguish itself from sibling get_discovery_manifest, leaving possible confusion between two manifest-like tools.

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 guidance about when to use this tool versus alternatives such as get_discovery_manifest or get_verified_offer. No when-to-use or when-not-to-use context is provided, which is a significant gap given the overlapping sibling names.

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