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

Annotations only declare destructiveHint=true, but the description adds substantial beyond-annotation behavior: the dump is transaction-consistent, no tables are locked, the site stays online during the run, the storage path, and the ordering of the returned list. That is exactly the operating detail an agent needs before mutating server state.

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?

Front-loaded with the core action and four tight sentences, each carrying distinct information. Minor redundancy between 'consistent backup' and 'transaction-consistent dump' costs it the top mark.

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?

An output schema exists so return values needn't be spelled out, yet the description still characterizes the reply's ordering. Combined with the when-to-use guidance, only the undocumented `server` parameter leaves a real gap.

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%, so the description must carry the load; it usefully explains that an empty `database` means back up everything, but it says nothing about the `server` parameter (which server, default behavior, or how to discover names). Partial compensation for a two-parameter gap.

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 precise verb+resource ('takes a consistent backup of the website's database') plus where it lands ('/data/backups'), and clearly distinguishes itself from site_db_restore and site_restore by naming the restore path as the consumer of its output.

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?

Explicitly sets the usage window: 'A nightly automatic backup already runs; this tool is for taking one right before a risky change.' It also gives the alternative route (feed the returned file name to site_db_restore), so the agent knows both when to call it and what to do next.

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