db_table_restore

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

Discloses key behaviors: default dry-run, need for confirm=True to write, and truncate_first deletes existing rows before inserting. Warns about danger of truncate_first. No annotations provided, so description fully covers behavior.

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?

Well-structured with brief intro followed by parameter list. Every sentence adds value, no fluff. Includes a crucial warning. Front-loaded with key purpose.

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?

Covers all important aspects: purpose, parameters, default behavior, and output (returns plan when dry-run). Output schema exists, so not describing return values is acceptable. Complete given tool 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?

Input schema has 0% schema description coverage, so description must add meaning. It does so by explaining backup_path as path from db_table_backup, confirm as needed for write, and truncate_first as deleting current rows. Adds significant value beyond bare schema names.

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?

Clearly states 'Restore a table from a JSON backup produced by db_table_backup', specifying verb and resource, and distinguishes from related siblings like db_table_backup and db_table_list_backups.

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?

Explains default dry-run behavior and when to use confirm=True and truncate_first=True, including a warning about the danger of truncate_first. Does not explicitly mention when not to use the tool, but context is clear.

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