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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real context beyond them: the report is free, is built from a verified signed publication on every read, expired observations are treated as historical, and it never starts checkout. These extras usefully set expectations about freshness and provenance.

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?

Front-loaded with the core purpose and then a compact enumeration of contents and behavioral constraints. It is somewhat dense and prose-heavy but every sentence carries information; nothing is redundant padding.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them. Combined with the provenance, freshness, and no-checkout details, the definition is complete enough for an agent to call it correctly; only an explicit sibling-routing rule is missing.

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 takes zero parameters, so there are no argument semantics to explain; per the rubric a 0-param tool gets a baseline of 4. The description does not need to compensate for any schema gap 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?

States a specific verb (Read) and a precise resource (Agent Shopping Check) scoped to a named product (Vuori Kore Short, Ink, US). The description enumerates the report's contents (product context, advertised claims, gaps, merchant fixes), so an agent knows exactly what artifact this returns. It is clearly distinguishable from siblings like get_publication or get_claim.

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?

Usage is only implied: the agent can infer this is a read-only report fetch and that 'Never pays or starts checkout' marks a boundary, but there is no explicit when-to-use, when-not, or named alternative among the many sibling tools (get_publication, get_claim, evaluate_x402_resource). No routing guidance is offered.

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