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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered, though the description redundantly repeats "Read-only." What it does add beyond annotations is genuinely useful: result ordering (newest first) and the shape of each returned record, including that share_url is null until shared. Pagination behavior for the limit parameter remains undisclosed.

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?

Two short sentences, both front-loaded with the most decision-relevant facts (scope and ordering first, return fields second). Nothing is wasted, though the "Read-only" clause duplicates the annotation.

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 simple zero-required-parameter list tool with no output schema, the description covers scope, ordering and the key returned fields, which is most of what an agent needs. The remaining gap is how limit affects the result set, which matters given the count is unbounded otherwise.

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?

The single parameter, limit, has 0% schema description coverage and the description never mentions it, so neither its meaning, default, nor maximum (100) is explained anywhere an agent would naturally look. Since coverage is far below 50%, the description should have compensated and does not.

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?

The description names a specific verb and resource ("List the caller's wishlists") plus scope ("from their active workspace") and ordering ("newest first"), which is more than a restatement of the name. It does not explicitly contrast with the many sibling *_list tools, but the resource noun alone makes the target unambiguous.

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?

There is no explicit when-to-use guidance, no mention of alternatives, and no note on when not to call it. The workspace scoping sentence hints at context but a reader must infer the conditions under which this is the right tool.

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