schema_diff

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

No annotations are provided, so the description carries the behavioral burden. It discloses the core non-mutating comparison behavior and the table_name scoping ('If empty, diff all tables'), which is helpful. However, it does not state whether the operation is strictly read-only, what happens if connections are invalid, or how many schema objects are processed, leaving some transparency 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 appropriately short and front-loaded. The first sentence states the purpose, and the Args block efficiently covers each parameter without redundancy. Every sentence earns its place.

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 is adequate for a straightforward diff tool: it names the two required connections and the optional table filter. An output schema exists, so return values need not be described here, but the description leaves unspecified what elements of the schema are compared and any prerequisites for connections, which an agent might need to know for correct usage.

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 0%, so the description compensates by explaining all three parameters. Source and target are described as connection names, and table_name receives additional semantics with the empty-means-all behavior. This goes beyond the bare schema titles, though it offers no examples or allowed values.

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 begins with a clear verb and resource: 'Compare schemas between two database connections.' This distinguishes it from sibling tools like get_schema or list_tables, which operate on a single connection, so the tool's specific role is immediately evident.

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 gives clear context: use this when you need to compare schemas across two connections, with an optional table filter. It does not explicitly name alternatives or exclusion conditions, but the purpose statement is enough to infer when it is appropriate.

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