Find MongoDB documents

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered; "read-only in every environment" is largely a restatement of that. The word "bounded" hints at enforced limits but the description never says what they are (max limit 200, default 50, timeout ceiling 120s), and it omits any note on cost, auth, or rate limits. Modest added value over the annotations.

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?

Two tight sentences with zero filler; the core operation and its controls are front-loaded, and the safety statement closes it out. Nothing needs to be trimmed or reordered.

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?

For a 9-parameter tool with nested free-form objects and no output schema, the description is thin: it never explains how filter/sort/projection documents should be shaped, omits response_format (which changes the return), and leaves connection_id/collection semantics to the schema. It is adequate but leaves real gaps an agent would hit in practice.

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% across 9 parameters, so the description carries the burden and does name five of the nine (filter, projection, sort, skip, max-time/timeout_ms), which is meaningful. However, it gives no syntax or shape guidance for the free-form filter/sort/projection objects, no mention of limit, connection_id, collection, or response_format, and no defaults or bounds.

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?

States a specific verb and resource ("Run a bounded MongoDB find query") and enumerates the query knobs, which cleanly separates it from siblings like mongo_aggregate and mongo_count_documents. An agent can identify the tool's job without opening the schema.

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?

There is no explicit when-to-use guidance or routing to alternatives. The agent must infer from the name that this is the document-retrieval tool versus mongo_count_documents or mongo_aggregate, and nothing states prerequisites (e.g., a valid connection_id from mongo_list_connections) or when not to use it.

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