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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by enumerating the returned payload (description, sizes/prices, availability, images, collections, ordering notes), which substitutes for the missing output schema.

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?

One front-loaded sentence that names the operation, the key, and the payload, with no padding or redundancy. Every clause earns its place.

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 simple read-only single-record lookup, the description covers purpose, key, and return content, and annotations cover the safety semantics. The only omission is explicit guidance on alternate discovery tools, which is minor given the straightforward scope.

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?

With one parameter at 0% schema description coverage, the description does some compensating work by stating the lookup key is a product 'handle'. It does not clarify the handle format (slug vs. numeric id) or behavior on unknown handles, so it only partially fills the schema 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?

The description gives a specific verb-plus-resource ('Full details for one product by handle') and even enumerates what those details are, so the agent knows exactly what comes back. It does not explicitly contrast with siblings like browse_catalog or list_collections, but the 'one product by handle' scoping makes the distinction inferable.

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: 'by handle' signals you need a known product handle, and 'one product' implies a targeted lookup rather than browsing. No when-not conditions or named alternatives (e.g. browse_catalog for discovery) are given, leaving the agent to infer when this beats a catalog listing.

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