atlas-get-performance-advisor

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

Annotations indicate readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds behavioral context: it includes a maximum of 50 slow query logs and lists the available operations. This goes beyond annotations by specifying scope and limits.

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 that efficiently captures the tool's purpose and details (operations, max logs). It is front-loaded and contains no redundant information.

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?

The description explains what the tool returns (recommendations and suggestions for each operation) and mentions a limit (max 50 slow queries). Given the tool has no output schema and all parameters are documented, this provides sufficient context for an agent to invoke the tool correctly.

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 100%, so the schema already documents all parameters well. The description does not add new meaning beyond what is in the schema (e.g., it repeats the ISO 8601 constraint for 'since'). Baseline 3 is appropriate.

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 retrieves MongoDB Atlas performance advisor recommendations, listing specific operations (suggested indexes, drop index suggestions, schema suggestions, slow query logs). It uses a specific verb 'Get' and resource 'performance advisor recommendations', and distinguishes from sibling tools which are unrelated.

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 explicit when-to-use or when-not-to-use guidance is provided. However, the description implies usage for performance tuning, and the tool name is self-explanatory. No alternatives are mentioned, but given the sibling tool set, it's clear this is the only tool for this purpose.

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