MCP Atlas

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

No annotations are provided, so the description carries the full burden. It mentions 'validate' but doesn't disclose behavioral traits such as whether it's read-only, if it modifies data, error handling, or output details. The description is minimal and fails to provide necessary context for safe and effective use.

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, efficient sentence that is front-loaded with the core purpose. There is no wasted language, and every word contributes directly to understanding the tool's function, making it appropriately sized and well-structured.

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 the complexity of migration validation (which could involve checks for consistency, integrity, and potential errors), the description is incomplete. With no annotations and no output schema, it lacks details on what the validation entails, what outputs to expect, or how to interpret results, leaving significant gaps for an AI agent.

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 (dirUrl, devUrl, format) with clear descriptions. The description adds no additional meaning beyond the schema, such as explaining validation logic or parameter interactions, but meets the baseline since the schema does the heavy lifting.

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's purpose with a specific verb ('validate') and resource ('migration directory'), specifying what it validates ('integrity and consistency'). It distinguishes from siblings like 'migrate-apply' or 'migrate-diff' by focusing on validation rather than application or comparison, though it doesn't explicitly name alternatives.

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 description implies usage for validating migration directories, suggesting it should be used before applying migrations or after creating them. However, it lacks explicit guidance on when to use this tool versus alternatives like 'migrate-lint' or 'migrate-status', and no exclusions or prerequisites are mentioned.

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