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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates state and searches externally. With no output schema, the description rightly discloses the returned fields (shopUrl share link, ownerUrl) and that each query is searched and added, but it says nothing about partial-failure behavior, idempotency, or whether the marketplace search could return empty results.

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-loaded with the core action and the return values, which is good. But 'curated host / hostess gifts gift wishlist' is garbled duplication, and the trailing 'OpenAPI: agentCreateAndFill' operation id gives an agent no actionable value.

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 10-parameter mutating tool with no output schema and thin annotation coverage, the description leaves too much implicit: six parameters (hostName, occasion, budgetBand, dietaryNotes, giftCategories, locale) are never discussed, and the required/optional ambiguity around marketplace is unresolved.

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 30% across 10 parameters, so the description carries a heavy burden it only partly meets: it names ASINs, keywords and search queries and bundles them as 'add in one call'. It says nothing about hostName, occasion, budgetBand, dietaryNotes, giftCategories, or locale, and never flags that marketplace is effectively required (0 required parameters at the schema level, yet the schema text calls it 'REQUIRED').

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 curated host/hostess gift wishlist and fill it with ASINs/keywords/queries) and names the return payload (shopUrl, ownerUrl). The phrase 'Preferred agent path: create a wishlist and add ASINs...' implicitly differentiates it from the create_wishlist + add_wishlist_item combo, though it never names those siblings outright.

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?

'Preferred agent path' gives a clear recommendation for when to reach for this tool: whenever creation and population can happen together. It lacks any when-not guidance (e.g., when to fall back to create_wishlist then add_wishlist_item), and the odd 'gift wishlist' framing narrows the apparent scope without explanation.

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