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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered elsewhere. The description adds no behavioral detail beyond them: it does not say whether one guide or a ranked list is returned, whether results are cached, or what 'most relevant' is based on.

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?

A single front-loaded sentence with the verb and object in the first few words and no filler. It is efficient, though the brevity is part of why the usage gap exists.

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, idempotent lookup with no output schema, the description is close to sufficient: 'the most relevant' implies a single best-match guide is returned. What is missing is routing guidance against the six sibling tools in this namespace.

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 100% and the schema already enumerates example topics (hard to shop for, cooking, games, self-care, weird gifts, under $25). The description adds nothing beyond restating 'gifting problem or topic', so the baseline 3 applies.

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 ('Find') and resource ('OhGiftPlease editorial gift guide') plus the input concept (gifting problem or topic). It implicitly distinguishes itself from find_gifts and browse_gift_categories by scoping to editorial guides, but it never names those siblings explicitly.

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?

'For a gifting problem or topic' suggests a trigger condition, but there is no explicit when-to-use guidance, no when-not-to-use, and no mention of the six sibling tools (find_gifts, browse_gift_categories, search_ohgiftplease) that an agent must choose between.

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