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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The phrase "the caller can open" adds a genuine hint about permission-scoped filtering, but the description says nothing about pagination behavior despite the after/limit parameters, nor about ordering.

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?

It is a single short, front-loaded sentence with no filler, which is good structurally. However, the brevity comes from under-specification rather than efficiency, and the phrasing "imported lists and results" is repetitious and imprecise.

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 list tool with four undocumented parameters and no output schema, the description should explain pagination, default ordering, and what a returned collection looks like. None of that is present, leaving the agent unable to call it correctly beyond a bare no-argument invocation.

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?

All four parameters (sort, after, limit, project_id) have 0% schema description coverage, so the schema supplies only bare names and types. The description compensates for none of it — it never mentions sorting, cursor pagination via after/limit, or whether project_id scopes the result set.

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?

"Lists the imported lists and results the caller can open" gives a verb and a rough resource, but the object is described circularly as "lists" and muddled with "results," so it is unclear whether collections are saved lists, saved searches, or query outputs. It offers no differentiation from close siblings such as get_collection, filter_collection, combine_collections, or list_collection_investigations.

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 when-to-use guidance at all: nothing says to call this to discover collections before get_collection or filter_collection, and no prerequisite or exclusion is stated. The agent must infer usage purely from the name.

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