create_metabase_collection

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

With no annotations provided, the description carries full burden but only states it 'creates' without detailing behavioral aspects. It doesn't mention whether this requires admin permissions, if collections are permanent or deletable, rate limits, or error conditions. The return type is mentioned but not elaborated.

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 well-structured with clear sections for Args and Returns. It's front-loaded with the core purpose, and each sentence adds value. Slightly verbose with 'Dict[str, Any]' but overall efficient.

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?

Given no annotations, 3 parameters with 0% schema coverage, and an output schema exists (though not shown), the description covers basics but lacks depth. It explains parameters and return type but misses behavioral context like permissions, side effects, or error handling that would be crucial for a creation tool.

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 0%, so the description must compensate. It provides clear semantics for all three parameters: name (required), color (optional hex code), and parent_id (optional parent collection ID). This adds meaningful context beyond the bare schema, though it doesn't explain format constraints like color validation.

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 clearly states the tool creates a new Metabase collection, specifying the verb 'create' and resource 'Metabase collection'. It distinguishes from siblings like 'create_metabase_card' or 'create_metabase_dashboard' by focusing on collections, but doesn't explicitly contrast with similar creation tools beyond naming.

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 like 'update_metabase_collection' or 'get_metabase_collection'. The description lacks context about prerequisites, permissions needed, or typical workflows involving collection creation.

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