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

Annotations already say it is a non-read-only, non-destructive, open-world, non-idempotent write. The description adds real behavioral context beyond that: a server-side enrichment step triggered by a product link, the overwrite precedence of explicit values, and the default status of 'idea'. It does not say what happens on duplicate entries or what the response contains.

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 tight sentences, front-loaded with purpose, then the enrichment/precedence rule, then the default. Every sentence carries distinct information with no filler.

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 7-parameter mutation with no output schema and partial schema coverage, the description covers the important behavioral risks: remote lookup from a link, overwrite behavior, and status defaulting. What is missing is whether the referenced person must already exist and what is returned after creation.

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 only 43% of 7 parameters, so the description must compensate, and it partly does: it explains link-driven enrichment, value precedence, and the status default of 'idea', and implicitly that currency falls back to the person's own currency. It says nothing about name, notes, or person_id semantics, so roughly half the parameters remain unexplained.

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 ('Adds a gift (or gift idea)') plus the scope ('for a person on the signed-in person's gift list'), and the parenthetical clarifies that both real gifts and ideas are covered. It does not explicitly distinguish itself from siblings like add_wishlist_item or create_gift_list, so it stops short of 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?

Clear context for how to call it: supply a product link to let the service populate fields, or pass values explicitly, with an explicit precedence rule ('anything you pass explicitly wins'). No exclusions or alternative-routing guidance (e.g. when to use update_gift instead) are given.

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