db_mongodb_query

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

The [SAFE] tag indicates non-destructive behavior, but no annotations exist. The description lacks details on side effects, permissions, or return characteristics, leaving the agent with minimal behavioral cues.

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 sentence with the safety tag front-loaded. It is concise but sacrifices necessary detail; no structure or segmentation is present.

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 three undocumented parameters, no output schema, and no annotations, the description is woefully incomplete. The agent lacks information on return values, filter syntax, and default behavior beyond the limit default.

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%, and the description does not explain any parameter. 'collection', 'filter', and 'limit' are left undefined, forcing the agent to guess their format and constraints.

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 it executes a MongoDB find query on a collection, specifying the verb and resource. However, it does not differentiate from siblings like db_mongodb_health or other query tools, missing an opportunity to clarify its specific read-only nature.

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. The sibling list includes many database tools, but the description offers no context for selection or exclusions.

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