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

Annotations already declare destructiveHint=true and openWorldHint=false; the description reinforces this by stating 'Existing data on the target is overwritten' and adds constraints the annotations lack (same-org, postgres-to-postgres engine match). It omits auth requirements and whether the operation is reversible, but the annotation coverage lowers the bar.

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?

Three tight sentences, front-loaded with purpose, then usage, then constraints. Every sentence carries information an agent needs; nothing is redundant.

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 destructive two-parameter mutation with no output schema, the description covers purpose, trigger scenario, engine/org prerequisites, and the overwrite consequence. Only minor gaps remain (no note on reversibility or expected outcome), which is acceptable given annotation coverage.

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 coverage is 100%, so backupId and targetServiceId are already fully documented, including the same-org constraint on the backup. The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (restore) and resource (backup) with precise scope: into a DIFFERENT deployment service in the same org. The 'different service' framing clearly distinguishes it from an in-place restore, though it never names the sibling nexusai_db_restore explicitly.

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?

Gives a concrete use case ('seed a new deployment from a snapshot of an old one') and a hard prerequisite (both services must use the same engine). It does not explicitly name the alternative tool (in-place restore) or state when NOT to use this one.

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