execute_mongo_find

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

The description adds 'validated' and mentions limits, which provides some behavior context. However, with no annotations, it fails to disclose error handling, read-only nature, or prerequisite connection state, leaving transparency gaps.

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, front-loaded sentence with no redundant wording. Every element contributes to the core purpose and constraints.

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?

While an output schema exists, the tool has no annotations and the description is too sparse for a 6-parameter operation. It omits parameter semantics and behavioral details, making it under-specified for reliable agent 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 description coverage is 0% and the description provides no information about parameters beyond the schema. It does not explain filter structure, defaults, or how limits interact, offering no added meaning for the six parameters.

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 executes a MongoDB find() operation, using the specific verb 'Execute' and resource 'find()'. It is distinct from siblings like execute_mongo_aggregate and validate_mongo_query, making the purpose unambiguous.

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 mention of row, byte, timeout, and concurrency limits implies controlled execution, but it does not explicitly state when to use this tool over alternatives or when not to use it. Sibling tools like execute_mongo_aggregate suggest a different scope, but the description lacks direct guidance.

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