export_backup

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

No annotations are provided, so the description carries the full burden. It only says 'Export DB to file' and does not disclose side effects such as whether outputPath is overwritten, whether tables filters the backup, whether schemaOnly affects behavior, or if this operation requires an active profile. The non-destructive nature of export is inferred but not stated.

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 with no wasted words, but it is under-specified for a tool with four parameters and many siblings. It is concise but not informative enough to fully earn its place.

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?

With four parameters, no annotations, no output schema, and a complex sibling set, the description is insufficient. It does not explain the required profileName, what tables does, or the output format. An agent cannot reliably invoke this tool correctly based on the current definition.

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% and the description adds no meaning for any of the four parameters (tables, outputPath, schemaOnly, profileName). An agent gets no help understanding what values to provide or how the parameters interact.

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 a specific verb ('export') and resource ('DB') with a destination ('to file'). This conveys the core action and loosely distinguishes it from profile or table-specific exports like export_profiles and export_table_csv, though 'DB' could be more precise regarding scope.

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 no guidance on when to use this tool versus the many sibling export tools (export_profiles, export_table_csv, export_sql_file). No alternatives, no conditions, no prerequisites are mentioned.

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