resync_tables

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 it's a write operation, triggers historical sync, and does not override standard sync frequency. However, it lacks details on whether it overwrites existing data, error conditions, or if it can be safely interrupted.

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 concise with three short sentences. It front-loads the warning and uses a symbol. Every sentence adds value with no redundancy.

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 write operation with three parameters and no output schema, the description is too brief. It does not explain the return value, error handling, or provide sufficient context about what 'historical sync' entails. It feels incomplete.

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 coverage is 100%, so the schema documents all three parameters adequately. The description does not add substantial meaning beyond the schema, only reiterating that the schema_file path must be read first. This meets the baseline of 3.

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 triggers a historical sync for multiple schema tables within a connection. It distinguishes itself from the sibling 'resync_connection' by specifying it operates on tables, but it could be more precise about what 'multiple schema tables' means.

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 warns to confirm with the user and notes it's a write operation, but it provides no guidance on when to use this tool versus alternatives like 'resync_connection' or 'reload_connection_schema_config'. No comparison with siblings or exclusions are given.

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