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

Annotations already establish readOnly=true and openWorld=false, and the description adds genuine behavioral detail beyond that: status lifecycle semantics (idea/bought/wrapped/done), the separate without_price group when a price filter is applied, and the dedup rule for from_wishlist claims. It stops short of describing ordering or result limits, which matters for a list tool with no output schema.

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?

Front-loads the core scope sentence, then statuses, then example queries, then edge-case semantics — a sensible information hierarchy with little filler. The example cluster is long and slightly redundant with the status list, but each example disambiguates a real filter combination.

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?

With eight optional params and no output schema, the description does the work of explaining what comes back ('matching gifts plus counts and totals') and how price-filtered results are partitioned. The main omission is pagination/limits and result ordering, which an agent would need before relying on counts.

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 100%, so the baseline is 3; the description earns extra credit by giving the enum statuses meanings the schema lacks (bought = 'bought but still needs wrapping') and by showing which filter combination each example question implies. Currency-conversion behavior is carried by the schema rather than the description, but that is a minor overlap gap.

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 and resource ('Searches the gifts the signed-in person (and their household) is giving across their current gift lists') and pins down the scope as gifts being given, which separates it from wishlist-oriented siblings. The closing note that from_wishlist items are claims rather than extra gifts further sharpens what this tool returns.

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?

Gives concrete when-to-use examples mapped to specific filters ('how many gifts still need wrapping?' → status bought, 'what's left to buy for the kids?' → person/newest default), which is stronger than generic 'use this to search' guidance. It does not explicitly exclude siblings such as find_wishlist_items or get_person_gifts, so there is a small residual routing gap.

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