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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description is redundant. However, the description adds genuinely useful behavior beyond the annotations: results come back in manual order, and a wrong-owner id returns empty rather than erroring — a detail that directly changes how an agent handles 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?

Three tight sentences, front-loaded with the verb, resource and scope before the return-shape note. The only waste is the 'Read-only.' fragment, which merely restates readOnlyHint=true, and that is a single word in an otherwise dense definition.

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's enumeration of item fields (title, url, note, price, currency, priority, reserved) is necessary and present, and ownership behavior is covered. The remaining gap is the undocumented 'limit' parameter, which matters for an agent paginating or capping large wishlists.

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 0%, so the description carries the burden. It clarifies that wishlist_id must reference one of the caller's own wishlists and that a foreign id yields an empty result, which is real added meaning. But 'limit' is never mentioned despite a 1–200 range in the schema, leaving half the parameters undocumented in every source.

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 ('List the items') plus a scoping constraint ('on ONE of the caller's wishlists (by wishlist_id)'), which disambiguates it from a list-all-wishlists style sibling and from mutation siblings like add_wishlist_item or create_wishlist. It stops short of naming any sibling explicitly, so an agent still infers the alternatives from names rather than being told.

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?

Usage is implied: call this when you have a specific wishlist_id and need its contents. There is no explicit when-not guidance and no mention of the 'limit' parameter, so an agent gets no instruction on truncation, defaults, or when to prefer another listing tool.

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