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

Annotations already declare destructiveHint=true, readOnlyHint=false, non-idempotent and open-world, so the safety profile is covered. The description adds real value beyond that by clarifying the tool only prepares a proposal ('Returns an existing release proposal, not execution authority') and confines itself to preview code with 'no Live change or data restore'.

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 tightly packed sentences with the core action front-loaded and zero filler. The density is effective, though the jargon ('closed stateless fixture', 'independently pinned static-export recipe') borders on cryptic.

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, non-idempotent mutation the description does cover scope, return semantics, and safety framing, and no output schema exists so return detail is minimal. However, with 0% schema coverage the unexplained expected_revision concurrency parameter leaves a gap an agent needs to call this 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?

Schema description coverage is 0% across four required params. The description hints at checkpoint_id ('exact checkpoint') and environment ('Preview'), but never explains expected_revision (apparently an optimistic-concurrency token) or app_id, and adds no format or constraint guidance. This materially under-compensates for the coverage 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 specific verb ('prepare ... restoration') and a precise resource/scope ('code-only restoration to isolated Preview from an exact checkpoint'). The narrowing clauses ('no Live change or data restore') help distinguish it from writing siblings like beon_create_app_checkpoint or beon_pin_app_checkpoint, though no sibling is named outright.

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 genuine applicability constraints ('Closed stateless fixture or independently pinned static-export recipe only') and an exclusion ('no Live change or data restore'), which tells an agent both when this applies and when it does not. It stops short of routing to alternatives (undo/redo/release), so it falls below a 5.

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