run_schema_check

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic action without detailing whether it is read-only, requires permissions, or what side effects exist. This is inadequate for safe invocation.

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 very short (two sentences) and front-loaded, but it sacrifices necessary detail. Conciseness is valued, but here it leads to incompleteness rather than efficiency.

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 two untyped object parameters, no output schema, and no annotations, the description fails to provide enough context for an agent to understand inputs, outputs, or behavior. It is not complete for the tool's complexity.

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 gives zero information about what 'source' and 'target' parameters represent (e.g., table names, connection strings). The agent cannot determine how to populate these objects.

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 states it compares table schemas (column names, data types), which is clear. However, it does not differentiate itself from the nearly identical sibling tool 'compare_table_structures', leaving potential confusion for the agent.

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 provides a brief 'USE' sentence but no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives. Given the similar sibling, this is insufficient.

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