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

Annotations only give readOnlyHint, so the description usefully adds that this is 'a read-only search' despite the POST verb — a non-obvious clarification — and discloses pagination behavior ('pass meta.next_page as page'). It does not describe return shape or result limits beyond what pagination implies.

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 terse clauses front-load the resource definition, filters, and pagination with no filler. Efficient and well ordered, though the parenthetical definition and endpoint note are tightly packed.

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 7-parameter, all-optional search tool with no output schema, the description covers the resource, filterable fields, and the pagination mechanism needed to call it correctly. It could say more about the returned result structure, but the essentials are present.

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 the schema already documents all seven parameters, making this the baseline 3. The description's filter list (ids, name substring, public) and pagination note merely restate what the schema provides without adding format or edge-case 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?

States a specific verb and resource ('List collections') and clarifies what a collection is ('sets of groups shown together'), which disambiguates from the sibling search_groups. It does not explicitly name alternative tools, but no sibling competes for the same resource.

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?

Implicitly frames this as a filtered search with pagination, and there is no sibling collection-search tool to route against, so usage is largely implied rather than stated. No explicit when-to-use or when-not-to-use guidance is given.

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