db_table_backup

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

Discloses output format, allowlist requirement for out_dir, and optional label. However, does not explicitly state non-destructive nature (likely read-only) or error handling. No annotations to supplement.

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?

Extremely concise: one clear sentence plus bulleted parameter descriptions. No fluff.

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 purpose, parameters, output, and constraints. With an output schema present, the description is sufficient for a simple backup tool. Minor omission: does not explain return value beyond file creation.

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?

Adds significant meaning beyond schema: lists permissible values for 'table', describes 'out_dir' constraint (safe allowlist), and explains 'label' as filename tag. Compensates for 0% schema description coverage.

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 the action (dump), resource (table), and output (timestamped JSON file). Lists supported tables, distinguishing it from siblings like db_table_restore 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?

Implies use for backups but lacks explicit guidance on when to use vs. siblings (e.g., restore, list). No mention of alternatives or exclusions.

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