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

Annotations already declare readOnly, non-destructive, non-open-world, so the safety profile is covered. The description adds genuinely new behavior beyond that: results are bounded and truncated explicitly, and saved-query execution/editing are out of scope. It stops short of explaining the truncation threshold or error behavior for an unknown id, so it is strong but not exhaustive.

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 short sentences, usage condition front-loaded, then return shape, then boundaries. No filler, no restatement of the tool name, and every clause carries information an agent needs.

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 carries return-value burden and does so reasonably by naming membership, pins, saved-query references, and truncation. It omits error/not-found behavior and does not quantify the bounds, which keeps it just short of fully complete for a read tool.

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?

There is one parameter with 0% schema description coverage; the schema only supplies a UUID pattern, not meaning. The description implies the parameter is the identity of a 'selected List' but does not restate or clarify the required UUID format or what happens if the id does not resolve. Baseline 3 for a thin single-param tool whose description adds only implicit meaning.

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 resource (a List's exact assets, authors, saved references) and what is returned (bounded membership, pins, saved-query references with truncation). It also explicitly distinguishes itself from the sibling query_list_activity and states which capabilities are not implemented, so an agent can tell it apart from neighbors without opening 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?

'Use when a selected List's exact assets, authors or saved references are needed for follow-up research' gives an explicit activation condition, and the follow-on sentence names the alternative (query_list_activity) plus the excluded operations (saved-query execution and edits). When-to-use, when-to-use-something-else, and what-not-to-expect are all present.

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