get_collections

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

The description clearly indicates a read operation ('List all'), so an agent can infer it is non-destructive. However, there are no annotations and no additional behavioral details such as pagination, permissions, or ordering. The lack of explicit safety disclosure is mitigated by the obvious read-only nature, but it could be more informative.

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?

The description is a single, front-loaded sentence with no fluff. It is concise and to the point, using the exact pattern 'verb + resource'.

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, the description 'List all collections in Metabase' is sufficient to convey the scope and purpose. There is no output schema, but the return value (list of collections) is reasonably implied. It could mention that it returns all collections without filtering, but 'all' already conveys this.

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 there are no parameter semantics to clarify. Per the rubric baseline for 0 params, this is a 4.

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 ('collections in Metabase'), clearly stating the tool's function. It distinguishes itself from sibling tools like get_configured_databases and get_database_metadata by targeting collections specifically.

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?

No guidance is provided on when to use this tool versus alternatives such as search_cards or search_dashboards. It does not mention e.g., 'use this to get all collections, or search_cards to filter'.

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