atlas-connect-cluster

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

The description says 'Connect', implying a mutating operation, but annotations declare readOnlyHint=true and destructiveHint=false, indicating a read-safe operation. This is a direct contradiction. The description does not disclose what the tool actually does (likely retrieve connection details) or any behavioral traits.

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?

Extremely short (one phrase) but not concise in a helpful way; it lacks necessary detail without being truly efficient. Could be improved without adding length.

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?

Despite having an output schema, the description fails to explain what the tool returns or how the connection is used. The minimal description is insufficient for a tool that likely provides connection strings or endpoints, especially given the existence of sibling 'connect'.

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 covers 100% of parameters. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already documents the three parameters adequately.

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 'Connect to MongoDB Atlas cluster' states the verb and resource but is vague. It does not differentiate from the sibling tool 'connect', and fails to clarify whether this tool establishes a connection or retrieves connection details, especially given the readOnlyHint annotation.

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 like 'connect'. No prerequisites, when-not, or context provided. The description offers no situational hints.

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