create_collection

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

No annotations are provided, so the description shoulders the full burden. It identifies the action as creation but does not disclose authentication needs, side effects (e.g., what parent_id validation does), or behavior on duplicate names. Minimal behavioral insight beyond the basic action.

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 short (one sentence plus a list) and front-loaded. It could be leaner by relying on the schema, but it is not overly bloated. The structure is acceptable for its length.

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 the tool's simplicity (4 params, output schema present), the description is adequate but missing usage guidance and behavioral details. The output schema covers return info, so that omission is acceptable. Overall, it feels incomplete for optimal agent decision-making.

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%, but the description lists parameters with types and optionality, essentially repeating the schema. It adds no extra context (e.g., color format, where parent_id comes from). The list is useful but does not deepen understanding beyond the schema.

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 'Create a new collection in Metabase.' This is a specific verb and resource. Sibling tools like list_collections and get_collection_items confirm this tool's unique role.

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 provides an Args list but no guidance on when to use this tool versus alternatives (e.g., create_card, create_dashboard). No prerequisites, exclusions, or preferred scenarios are mentioned.

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