backup_dataset

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

Annotations only cover idempotentHint, so the description carries most of the burden and delivers real detail: it produces a timestamped JSON file, writes to ~/.quicksight-mcp/backups/, and lists what the payload contains (SQL, columns, physical/logical table maps). It stops short of stating permission requirements or failure modes for large datasets.

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 action and outcome are front-loaded in the first sentence, followed by concise supporting detail on file format and location. Slightly padded by the parenthetical field list, but nothing is wasted.

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 one-parameter, low-risk tool with an output schema, the description supplies the essentials an agent needs: what is captured, the file format, and the on-disk location. It lacks only guidance on when the backup should be preferred over related read tools.

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?

Only one parameter and schema description coverage is 100%, so the schema fully documents dataset_id. The description adds no syntax or format detail for it, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (save/backup) and resource (QuickSight dataset configuration) with a clear target (disk). It is distinguishable from sibling tools such as get_dataset (read), snapshot_analysis/backup_analysis (analyses, not datasets), and restore_analysis.

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?

Usage is implied (back up a dataset before mutating it, given siblings like update_dataset_sql and update_dataset_definition), but the description never says when to use this versus get_dataset, snapshot_analysis, or backup_analysis, and names no exclusions or prerequisites.

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