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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real value: it discloses the required meta/ucp-agent profile, the subset constraint on results, and the failure mode (ucp.status error plus not_found). That failure behavior is exactly the kind of context annotations cannot convey.

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 definition is a single dense run-on that leads with protocol version and internal namespace (2026-08-25, dev.ucp.shopping.catalog.lookup) before saying anything actionable. Critical usage and parameter facts are compressed into clause chains rather than front-loaded or separated, making it hard to scan.

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?

Given an output schema exists, the description need not detail return shape, and it adds the important subset/error semantics. Still missing for a two-parameter protocol tool is any statement of how catalog.context and catalog.filters change results, plus guidance on distinguishing it from the six or so catalog/pricing siblings.

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?

Schema coverage is 0% and the schema properties are empty objects, so the description carries the full burden and largely does: it explains meta as {ucp-agent: {profile}} and catalog as {id: a GTIN or <market>:<gtin14> variant id, context, filters}. The residual gap is that it calls meta required while the schema declares zero required parameters, and it never explains what context or filters accept.

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?

It identifies the resource and domain (UCP product detail, catalog lookup) and states what comes back (variants per market, list price, claim_status). However, the actual verb is never stated plainly, and nothing distinguishes it from siblings such as get_item, get_price, lookup_catalog, or search_catalog. The purpose is recoverable but buried under protocol jargon.

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 explicit when-to-use guidance and no named alternative; an agent cannot tell from this text whether to call get_product or get_item/lookup_catalog for a given lookup. The only conditional described is the outcome when the product falls outside the priced subset (error, not_found), which is behavior rather than selection guidance.

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