recovery_open

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating, potentially destructive operation. The description's only behavioral detail is 'without closing existing tabs' and the opaque 'clear the fence' clause; it never says what state is overwritten or destroyed, what preconditions exist, or what 'fence' refers to. With annotations carrying the safety signal, the description adds little that is intelligible.

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?

It is a single compact sentence with the verb front-loaded, so it is short. But the second clause is dense, undefined jargon rather than useful information, so brevity comes at the cost of clarity.

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, single-parameter tool with no output schema and no schema descriptions, the description should explain the input, the destructive consequences, and the preconditions. It supplies none of these, leaving key details to inference.

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 schema has one required parameter, 'path', with 0% description coverage, so the description must compensate. It never mentions 'path' or explains what the string points to (a checkpoint file, an identifier, a URI), leaving the only input completely unexplained beyond its name.

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 opening clause gives a concrete verb and resource: 'Open a workspace native checkpoint.' However, 'native checkpoint' is never distinguished from the checkpoint_* and recovery_* siblings, and the trailing clause ('clear the fence only after its complete recorded model matches') introduces undefined jargon ('fence') that muddies rather than clarifies the action. An agent can guess the general operation but cannot reliably tell it apart from recovery_restore or checkpoint_restore.

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 offers no when-to-use guidance and does not compare itself to any of the many recovery_* and checkpoint_* siblings. The phrase 'without closing existing tabs' describes a side behavior, not a selection criterion, so an agent has no rule for choosing this over recovery_restore.

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