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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real value beyond that by enumerating the return fields (id, editToken, ownerUrl, shopUrl, wishlist, storage) and by warning that token storage can cause later mutations to return a new id. That id-instability caveat is exactly the kind of behavior annotations cannot express.

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?

Dense and front-loaded: purpose first, then return shape, then the critical token caveat. The trailing 'OpenAPI: createWishlist' is filler that adds nothing for an agent, and the run-on return-field list is terse to the point of being hard to parse.

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?

There is no output schema, so the description usefully covers return values and the editToken lifecycle, including a downstream-compatible warning about changing ids. What it lacks is any guidance on the input parameters, which is a gap for an 8-parameter tool, though the enum values are largely self-describing.

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?

With 8 parameters and only 25% schema description coverage, the description must compensate for the semantics gap, but it explains none of them — marketplace, locale, occasion, budgetBand, styleTags, relationship, and recipientName are never mentioned. Its only parameter-adjacent note concerns the returned editToken, which is output, not input.

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 ('Create a girlfriend/wife gift list / wishlist') plus its use case ('shopping-list building'), which is far more than the name/title alone. However, it never distinguishes itself from the sibling create_and_fill, which an agent could plausibly confuse with a create-and-populate operation.

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 one concrete workflow instruction ('Save editToken for add_wishlist_item'), which implies the create-then-add-items sequence. But there is no explicit when-to-use/when-not guidance and no routing between create_wishlist, create_and_fill, and add_wishlist_item, so the agent must infer the choice.

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