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

Annotations already flag the tool as destructive, and the description adds substantial context beyond them: exactly what is destroyed, that only the current workspace is affected, the production restriction, and that fixture reseeds create an audit trail via logged commands.

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?

The description is front-loaded with the core action and remains fairly tight. The final 'Effects:' sentence partly repeats the earlier deletion statement, but the reinforcement is useful for a destructive operation.

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, zero-required-parameter reset tool with no output schema, the description covers scope, effects, environment restriction, optional fixture behavior, and audit consequences. An agent has enough information to decide whether and how to call 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?

Schema coverage is 100%, so the schema already documents the fixture parameter. The description adds meaningful semantics by explaining that fixtures are command scripts replayed into the workspace, producing an audit trail, which goes beyond the schema's brief parameter note.

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 and resource: 'Wipe THIS workspace and optionally reseed it from a named fixture.' It also scopes the action to the current workspace only, distinguishing it from anything global.

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?

It clearly states a key usage constraint—available only outside production—and explains the optional fixture reseed path. It does not explicitly compare against sibling tools such as core_replay_scenario, so it falls short of full when-to-use/when-not guidance.

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