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

It discloses operational behavior beyond the annotations: the catalog is live, has ~20k positions / ~2k unique items across named categories, requires throttling (~1s spacing), and warns against assuming a SKU. The annotations already declare read-only and idempotent, and the description adds rate-limit and data-freshness context that is genuinely useful.

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 terse but dense with signal: endpoint, catalog scope, categories, optional query, downstream purchase usage, rate-limit advice, and an anti-SKU caveat. Every clause earns its place and important constraints are front-loaded.

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 list tool with no output schema, it covers the essential context: live catalog scope, optional query, rate limiting, and how the results relate to purchase_gift via offer_id and ext_id. The main gap is that query semantics and return shape are implied rather than explicitly described.

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%, so the description must compensate for the undocumented query parameter. It only says 'Optional query string,' which adds little beyond the schema's property name and optionality. It does not explain what the query filters on, what syntax to use, or how it affects results.

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 identifies the resource as a live gift catalog and enumerates categories, and it is clearly distinguishable from the sibling purchase_gift because it is positioned as the catalog lookup that feeds purchase_gift. However, the action 'list' is carried mainly by the name/title; the description itself is fragmentary rather than a direct verb statement.

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?

The description gives clear usage context: call this before purchase_gift, pass offer_id + ext_id to purchase_gift, and space catalog calls ~1s apart. It does not explicitly state when not to use this tool or name an alternative tool, but the sequential instruction is strong enough.

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