compare_schemas

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

With no annotations provided, the description carries the full burden. It discloses that the tool outputs ICE-scored differences and is used for migration planning, but it does not state whether the operation is read-only, any side effects, permissions needed, or what ICE-scored means. This adds some context beyond the name but leaves notable 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 that efficiently conveys the action, resource, and purpose without fluff. Every word contributes value, making it highly concise 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?

For a tool with 4 required parameters, no output schema, and no annotations, the description provides a clear purpose and mentions the ICE-scored output. However, it leaves some gaps: 'ICE-scored' is unexplained, and the phrase 'between environments' could be more precise given that the actual parameters are database IDs. Overall, it is fairly complete but not exhaustive.

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?

The schema descriptions cover all 4 parameters (100% coverage), so the baseline is 3. The description adds no parameter-specific details beyond the general 'between environments' concept, which is already reflected in the schema's environment enums.

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 verb (Compare), the resource (database schemas), and the scope (between environments), while also specifying the purpose (detect drift, plan migrations) and the distinctive output (ICE-scored differences). This effectively differentiates it from sibling tools like analyze_database_schema or validate_database_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?

The description implies when to use the tool (comparing schemas across environments for drift detection or migration planning) and provides clear context. However, it does not explicitly mention when not to use it or name alternatives, which would elevate it to a 5.

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