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 by enumerating the return payload (id, editToken, ownerUrl, shopUrl, wishlist, storage) and flagging the critical token-continuity requirement for add_kit_item. It omits permissions, whether ownerUrl/shopUrl make the list publicly reachable, and rate limits, so it falls short of full disclosure.

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 compact sentences, front-loaded with purpose and return fields, then workflow guidance; every clause carries information. 'OpenAPI: createWishlist' is marginally useful metadata rather than agent-facing guidance, a minor bit of 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?

The description covers the creation semantics and return shape well, which matters given there is no output schema. But for an 8-parameter mutation tool with 25% schema coverage, the input side (what moveType, budgetBand, roomFocus, cityHint, householdName actually influence) is left unexplained, so an agent can call it but cannot call it well.

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 and does not — it says nothing about marketplace, items, cityHint, moveType, roomFocus, budgetBand, or householdName. The nested items array (url/asin/name/emoji/catalogId/searchKeywords) is entirely undocumented, leaving an agent to guess how to seed a kit.

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 housewarming / first-apartment kit list' — which is unambiguous and clearly distinct from add_kit_item (appends to an existing kit) and create_and_fill (one-shot variant). It even maps to the backing OpenAPI operation (createWishlist), removing any doubt about what gets created.

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?

'Prefer create_and_fill for one-shot' and 'Save editToken for add_kit_item' give an explicit alternative plus the follow-up workflow, implying this tool is for incremental kit building. It stops short of a full when-to-use statement (e.g. what to do when items are already known), but the routing signal is clear.

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