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

With zero annotations the description carries the full burden, and it does disclose auth scope requirements and a specific refusal behavior (403 for unclaimed sandbox workspaces), which is genuinely useful pre-call context. It omits ordering, pagination/truncation behavior for the 500-row cap, and whether the listed price is cached or live.

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?

Three short sentences, purpose front-loaded, no filler. The repeated 'Needs a ... Needs a ...' construction is slightly mechanical but each sentence carries a distinct constraint.

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 one-parameter read-only list tool with no output schema, the description covers what is returned, auth prerequisites, and the main failure mode. A brief note on result ordering or what happens when the catalog exceeds limit would make it fully self-sufficient.

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 single parameter 'limit' is fully documented in the schema (max 500, default 100), so the schema does the work. The description adds nothing about how limit interacts with total catalog size or whether results are truncated silently; baseline 3 applies at 100% coverage.

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 and resource ('List the catalog items the commerce pipeline tracks for your workspace') and even describes the returned fields ('each product the cycle prices, with its current price and source'). It never distinguishes itself from the ambiguous sibling browse_catalog or list_product_categories, so it falls short of a 5.

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?

Gives explicit preconditions for a successful call: a Last Price credential with commerce catalog read scope and a claimed workspace, with the concrete failure mode (403 on sandbox keys until claimed). It does not say when to prefer this over sibling browse_catalog, so no exclusions are offered.

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