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 disclosing the returned identifiers, that editToken must be persisted, and that storage='token' can cause later mutations to return a new id — a non-obvious stateful behavior. It still omits error behavior and whether items pre-populate the list.

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 action and return shape, then the critical constraint, then the workflow caveat — every sentence carries signal. 'OpenAPI: createWishlist' is low-value metadata but costs almost nothing.

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 no output schema, the description correctly enumerates the return fields and explains the token lifecycle, which is what an agent needs for a creation call. The remaining gap is the un-described personalization parameters on a 10-parameter mutation tool.

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 only 20%, so the description must carry the burden, yet it only reiterates that marketplace and locale are required — already encoded in the schema's required array. Eight of ten parameters (dadType, hobbies, styleTags, budgetBand, occasion, relationship, recipientName, items) get no semantic explanation, leaving the agent to infer intent from names and enums alone.

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 (creates a wishlist) and names the return payload fields, so the agent knows exactly what the call produces. It also ties forward to add_item, giving a hint of how it fits among siblings. The only imprecision is the mismatch between 'Father's Day wishlist' and the broader 'occasion' enum (birthday, retirement, just-because).

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?

'ALWAYS pass marketplace + locale' is an explicit invocation rule, and 'Save editToken for add_item' gives clear follow-up workflow guidance. It does not say when NOT to use this tool or point to alternatives like search_gifts/add_item, which keeps it below a 5.

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