compare_schemas

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

No annotations are provided, so the description must fully disclose behavior. It states the tool compares schemas and shows differences, implying a read-only operation, but does not explicitly confirm it is non-destructive, mention any permissions needed, or describe performance implications. The behavioral disclosure is minimal.

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 communicates the core purpose. It has no fluff, though it could be slightly more structured. It earns its space.

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 no output schema, the description briefly mentions what is shown (tables, columns, indexes) but lacks detail on the output format or structure. With 4 well-documented parameters and moderate complexity, the description is adequate but leaves some gaps for an agent to infer.

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 input schema has 100% coverage, meaning all 4 parameters have descriptions. The description adds little beyond the schema—it mentions that the tool shows tables, columns, and indexes, but does not enhance parameter understanding. 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 compares schemas between two databases and shows differences in tables, columns, and indexes. It gives a specific use case (dev vs prod comparison), making it distinguishable from sibling tools like list_schemas or get_table_stats.

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 mentions it's 'useful for dev vs prod comparison' but does not explicitly state when to use it vs alternatives, nor when not to use it. It lacks exclusions or prerequisites, leaving usage implied rather than guided.

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