Create a Micro record backup

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

Annotations already indicate this is a mutating, non-idempotent, non-read-only operation. The description adds meaningful behavioral context by specifying that the snapshot is 'bounded', 'transactional', and excludes authoritative identity, payment, entitlement, product, file, and deployment resources. This clarifies scope beyond the raw readOnlyHint/idempotentHint flags. No contradiction with annotations.

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?

Two sentences with no filler. The core action and resource are front-loaded, and the exclusion list is given in a compact second sentence. Every word adds useful constraint information.

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?

Given the annotations, full parameter schema, and presence of an output schema, the description covers the key behavioral boundary (record-only snapshot with explicit exclusions). It could go slightly further by noting the relationship to restore/delete backups, but nothing essential to invoking the tool correctly is missing.

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%, so the schema fully documents the two parameters ('path' and 'confirm'). The description adds no parameter-specific semantics, but the schema already carries that burden. 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?

The description states a specific verb ('Create'), a resource ('bounded transactional snapshot of the linked project's records'), and the key boundary (excludes identity, payment, entitlement, product, file, and deployment resources). This clearly differentiates the tool from restore/delete/list backup siblings without needing to open schemas.

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?

The description provides clear context: use it when you want to create a record-only snapshot of the linked project. It does not explicitly name alternatives like micro_backup_restore or micro_backup_delete, but the create/backup semantics and exclusion list make the intended use obvious. It lacks an explicit when-not-to-use statement.

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