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

Beyond the annotations, the description discloses important behavioral traits: paid-account requirements, refusal while another upload/export/restore is pending, a per-account cap, asynchronous polling behavior, and a specific failure mode. These are material operational details not captured by the readOnly/destructive/idempotent hints.

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 compact and front-loaded: it states the action first, then constraints, then the follow-up workflow. Every sentence carries operational information without repetition.

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 an asynchronous export-start tool with no output schema, the description supplies the essential lifecycle context: prerequisites, blocking conditions, polling target, next call, and failure signal. It gives the agent enough to invoke and follow up correctly.

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?

The description never mentions the required path object or its backupId/serverId fields, so it adds no meaning beyond the schema. Although the nested schema descriptions identify backupId and serverId sources, the top-level path parameter is undocumented and schema description coverage is reported as 0%, leaving the description to compensate and it does not.

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 uses a specific verb and resource: it packages a backup into a downloadable archive. It clearly distinguishes this from sibling tools like getBackupDownloadUrl and listBackups by describing startBackupExport as the step that initiates the export process.

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?

It gives explicit when-to-use and workflow guidance: poll listBackups until exportState is ready, then call getBackupDownloadUrl, and treat a return to idle as failure. It also states prerequisites (paid account and balance) and concurrency restrictions.

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