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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the burden of disclosure and does it well: it names the per-item fields returned (whose list, when added, claim state), states that results include counts by claim status overall and per person, and explains the non-obvious edge case that a price filter pushes unpriced items into a separate without_price group. These are behavioral traits the annotations and schema cannot convey, especially with no output schema.

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 scope sentence and then the exclusion, which is the right order, and every example maps to a real parameter combination rather than filler. The opening sentence is a long chain of clauses and the price-filter caveat sits late, so it is dense rather than trim.

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 eight optional parameters, no output schema, and only two weak annotations, the description supplies exactly what is missing: the return shape, the aggregate counts, and the price-filter edge case. The only unaddressed element is the must_have_only flag, a minor omission for an otherwise self-contained definition.

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 88%, so a baseline of 3 applies, and the description earns the bump by showing how parameters combine ('person plus added_since', 'claim_status claimed_by_me') and by clarifying that max_price drives the without_price grouping. The one gap is must_have_only, which is left unexplained in both the schema and the description, so an agent still cannot tell what it filters.

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 ('Searches the wishlists of other people in the signed-in person's wishlist groups') and immediately scopes it against the obvious confusable tools with 'Never includes the signed-in person's own lists.' That single exclusion separates it from get_my_wishlist and list_my_wishlists without the agent needing to inspect any schema.

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 four concrete question-to-parameter recipes (person plus added_since for 'what's new', max_price with claim_status for unclaimed ideas, claim_status claimed_by_me for 'what have I claimed?'), which is unusually actionable. It stops short of naming an alternative sibling for the excluded own-list case, so the agent must infer that get_my_wishlist is the fallback rather than being told.

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