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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-reach semantics are covered. The description adds only that results are paginated and that marketplace/locale are mandatory. It says nothing about auth requirements, rate limits, or how the curated set is ordered.

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, zero filler, with the pagination/curation scope front-loaded and the routing rule immediately after. Every sentence carries actionable information.

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 9-parameter, open-world read tool with no output schema and 33% schema coverage, an agent still cannot tell what q does versus genre/genres, what budgetBand accepts, or what a returned catalog entry looks like. The description covers only invocation basics, not enough for confident correct calls.

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 33% across 9 parameters, so the description must compensate and largely does not. It only restates the two required parameters, which the schema's required array and per-field descriptions already state. Contentious fields like genre vs. genres, budgetBand, platform, q, and offset/limit receive no explanation in either place.

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?

"Paginated curated gaming starters" plus the title gives a reasonably specific resource (curated catalog) and scope (paginated). The description also distinguishes it from the sibling search_gifts by declaring search as primary discovery, so an agent can tell the two apart. The word "starters" is slightly ambiguous about what a catalog entry actually is, which keeps it below 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?

It explicitly routes the agent: search_gifts is primary discovery, implying this is the browse/curated fallback path. It also adds a hard invocation rule, "ALWAYS pass marketplace + locale." It stops short of explaining when this beats get_wishlist or list_marketplaces, so no exclusion guidance beyond search.

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