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

With no annotations, the description carries the full burden and discloses very little: it does not say whether the rollback is itself reversible (no redo), what permissions are required, what state is returned, or how failures are reported. The '(§14)' reference points to an external specification an agent cannot read, so it adds no actionable behavior.

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?

A single front-loaded sentence with no filler, which is appropriate for a narrow operation. The trailing '(§14)' is cryptic clutter that references an unavailable document rather than earning its place.

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?

This is a state-mutating rollback with no annotations, no output schema, and an undocumented parameter, which raises the bar for the description. It omits scope of the rollback (which operation classes can be undone), reversibility, and error behavior, so an agent cannot predict the effect of calling it.

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?

There is one required parameter, projectId, at 0% schema description coverage, so the description must compensate. 'Applied to a project' only weakly implies what the identifier denotes (project ID vs. name or handle) and gives no format or example, leaving the sole parameter under-specified.

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 and resource ('Undo the most recent operation applied to a project') and bounds it to a single, most-recent operation, which separates it from siblings like project.update or project.get_state. It does not explicitly distinguish it from the conceptually similar storyline.rewind in the sibling set, so it falls short of a 5.

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?

Usage is only implied by the word 'Undo' and the 'most recent' scoping; there is no statement of when to prefer this over a manual project.update, nor when-not to use it. Nothing says whether undo is single-level or stackable, or what happens when there is no prior operation.

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