get_collections

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

With no annotations, the description carries the transparency burden. It discloses what the output includes (article counts, AI overview themes) but does not explicitly state side effects, authentication, or scope limitations (e.g., read-only). For a list tool, the mutability is implied as low, but the description could be more explicit about any filters or pagination.

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?

A single, well-formed sentence that leads with the action and includes the key output aspects. No wasted words or redundancy.

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 zero-parameter list tool without an output schema, the description is fully complete. It states what the tool returns (all collections with counts and themes) and is sufficient for an agent to invoke it correctly.

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 has zero parameters, so schema coverage is 100% by definition. The description adds no parameter details but is not required to; the baseline of 4 applies.

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 uses a specific verb ('List') and resource ('all your Collections') with concrete output details ('article counts and AI overview themes'). It clearly distinguishes from siblings like get_collection_overview by indicating the scope is all collections rather than a single one.

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 description clearly indicates this tool is for listing all collections, providing clear context for when to use it. It does not explicitly mention alternatives or exclusions, but the scope 'all your Collections' implies the primary use case and differentiates it from collection-specific tools.

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