List collections

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds real context beyond that by disclosing the returned fields, including aggregate member constraints (smallest context window, tightest rate limits) — non-obvious derived data an agent would otherwise have to discover empirically.

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?

One front-loaded sentence plus a short call-to-action sentence, with no filler. The parenthetical of aggregate properties is dense but each item earns its place by telling the agent what comparison data is available.

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 the burden of describing return contents and does so field-by-field, which is adequate for a no-arg discovery tool. It stops short of explaining ordering or how the 'what each is for' text should be interpreted for selection, but nothing essential for invoking it is missing.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly omits parameter discussion.

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 states the resource (the collections this Benchwarmers server offers) and enumerates the metadata each entry carries (name, purpose, tags, members, seats, reply mode, aggregate limits), which makes clear this is a discovery/enumeration tool. Combined with the title 'List collections' the intent is unambiguous, though the description itself never uses an explicit verb like 'list' or 'returns'.

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?

'Pick by task before calling ask' gives explicit routing guidance: call this first to choose a collection, then invoke ask. It does not address the other siblings (verdict, pending_verdicts) or say when not to use it, so it stops short of full when/when-not coverage.

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