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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely useful behavior beyond annotations: only PUBLIC collections of the target are returned, plus the identifier requirement. It does not say what happens when neither username nor userId is supplied (schema marks zero required params), which is the main undisclosed behavior.

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, purpose first and prerequisite second, with zero filler. Nothing could be removed without losing information.

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 5 parameters, no output schema and annotations present, the description covers the core purpose and the privacy scope, which is the important part. It is thin on the identifier-resolution behavior (what username vs userId does, what happens if neither is passed) and gives no hint about the returned list shape or pagination contract, which matters more here since there is no output schema.

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 100%, so limit, cursor, offset, userId and username are all documented in the schema and the baseline is 3. The description only restates that one of the two identifier parameters is needed, which marginally clarifies the identifier pair but conflicts with the schema's 'required: []' and adds no syntax or format detail.

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?

Names a specific verb (List) and resource scope (another user's public shelf groups), and the phrase 'another user's' is exactly what separates it from the sibling list_my_collections. An agent can pick correctly without opening either schema, despite the minor terminology drift between 'shelf groups' and the sibling convention 'collections'.

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?

The second sentence gives a prerequisite ('Requires username or userId'), which is useful routing context, but there is no explicit when-to-use / when-not-to-use guidance and no mention of list_my_collections as the alternative for the caller's own collections. Usage is implied rather than stated.

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