create_mongodb_card

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

With no annotations provided, the description carries the full burden. It only states the creation action and return value, but omits behavioral details such as required permissions, data validation, side effects, or error handling. This is insufficient for an agent to understand consequences.

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 a title, Args list, and Returns. It is concise, front-loading the purpose, and every sentence adds value without 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?

Given the tool has 7 parameters and an output schema exists, the description covers the basic purpose but lacks context on prerequisites (e.g., database must exist), error conditions, and how it fits with sibling tools. It is minimally complete.

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 coverage is 0%, so the description must compensate. It adds brief explanations for each parameter (e.g., 'MongoDB query string (aggregation pipeline or query)'), which gives meaning beyond the schema. However, some parameters like 'visualization_settings' could be more detailed.

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 explicitly states 'Create a new MongoDB question/card in Metabase', which is a specific verb-resource combination. It clearly distinguishes from sibling tools like 'create_card' (general) and 'create_model' (different resource).

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 on when to use this tool versus alternatives such as 'create_card' or 'execute_mongodb_query'. The description implies it is for MongoDB cards but does not provide any context on prerequisites or preferred scenarios.

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