Compare Tables

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

No annotations are provided, and the description is too brief to disclose behavioral traits. It does not state whether the tool is read-only, performance characteristics, or what the output looks like. For a tool with zero annotations, this is insufficient.

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 short sentence, which is concise but lacks essential structure. It does not front-load key information or earn its place with multiple useful sentences.

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 tool has 5 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain return values, error conditions, or how the comparison results are presented, leaving the agent with insufficient context.

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%, yet the description adds no parameter-level guidance. It does not explain the role of 'profile', 'leftSchema', 'rightSchema', or what 'visible tables' means in terms of the required 'leftTable' and 'rightTable' parameters.

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 action 'compare two visible tables' and lists the aspects: columns, indexes, constraints, partitions. This distinguishes it from sibling tools like ob_compare_schemas and ob_compare_metadata_snapshots. However, 'visible tables' is ambiguous and could be clarified.

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 guidance on when to use this tool versus other compare tools (e.g., ob_compare_schemas, ob_compare_query_results). No prerequisites or exclusions are mentioned, leaving the agent without decision context.

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