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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) by disclosing that it opens a backup run, that it may auto-add the barman-cloud archiver and restart DB instances one at a time (brief primary failover), and that the result includes a not_carried field. This is exactly the kind of side-effect and consequence detail a mutation tool needs.

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?

Dense but front-loaded: the core action comes first, followed by follow-up and caveats. Every sentence carries operational weight (follow-up tool, output caveat, failover warning, permission), though the single-block paragraph could be slightly tighter.

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?

Despite no output schema, the description covers the salient result (not_carried), the follow-up tool for tracking the run, the permission requirement, and a critical side-effect scenario. For a non-idempotent mutation tool this is sufficiently complete.

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 100% and the schema already explains each parameter (databases, persistent_volume_claims, vault_id, etc.) in detail. The description adds no parameter-level meaning beyond what the schema provides, so the 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+resource ('Take a restore point of a stack now') and anchors it with two aliases the agent may encounter (the CLI twin and the phrase 'back up shop now'). This clearly distinguishes the create action from siblings like get_restore_point, list_restore_points and restore_restore_point_in_place.

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 strong operational context: watch the resulting run with get_data_run, report not_carried, and warn the user before confirming on CloudNativePG stacks. It also states the required 'backups.operate' permission. It does not explicitly name when NOT to use it versus the restore-point alternatives, keeping it short of a 5.

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