execute_mongodb_query

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

With no annotations, the description carries full burden. It only says 'Execute' and returns results, but omits behavioral traits such as whether the query is read-only (likely safe), mutability, side effects, error handling, or performance considerations.

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 concise, using a clear docstring format with Args and Returns sections. It front-loads the main purpose and avoids unnecessary words.

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 complexity of MongoDB native queries and the presence of an output schema, the description covers basic parameters and return value. However, it lacks details on the query format, native_parameters usage, and typical response structure, which are important for correct invocation.

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's parameter explanations add value. Each parameter (database_id, collection, query, native_parameters) is described in the docstring. However, the 'query' parameter format (aggregation pipeline or query object) is mentioned but could be more precise.

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 'Execute a MongoDB native query against a Metabase database,' specifying the verb (execute), resource (query), and context (MongoDB/ Metabase). This distinguishes it from siblings like execute_query (likely SQL) and execute_card (card execution).

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 defines parameters but does not explicitly state when to use this tool over alternatives like execute_query or create_mongodb_card. It implies MongoDB usage but lacks explicit when-to-use or when-not-to-use guidance.

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