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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are paginated and curated, which is useful, but says nothing about page-size defaults, total counts, or the behavior of the redundant giftCategory vs giftCategories fields. "OpenAPI: getCatalog" is a docs pointer that adds no behavioral information.

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 with the resource description front-loaded and the invocation rule second. "OpenAPI: getCatalog." is low-value filler that does not earn its place for an agent caller, keeping this from a top score.

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 an 8-parameter read tool with no output schema and only half the parameters described, the description is thin: it never explains pagination semantics, the limit default of 24, or how the two gift-category parameters interact. An agent can call it correctly for the required-parameter path but will likely guess on filtering.

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 description coverage is only 50%: limit, offset, giftCategory and occasion are undocumented in both schema and description. The only parameter guidance, "ALWAYS pass marketplace + locale," merely restates the schema's required list, and the description does nothing to disambiguate the overlapping giftCategory (enum) and giftCategories (comma-separated string) parameters — the single most confusing aspect of this schema.

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 precisely — a paginated curated set of host gift starters — which is distinct from search-based discovery. It lacks an explicit verb (list/get) and never states what a 'catalog' entry actually is, but an agent can tell it apart from search_gifts and the wishlist siblings.

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?

"Search remains primary discovery" implicitly steers agents to search_gifts for discovery and to this tool for curated browsing, and "ALWAYS pass marketplace + locale" is an invocation rule. However, there is no explicit statement of when this tool is preferred over search_gifts, nor any exclusion or precondition beyond the required parameters.

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