reset_demo

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses what is destroyed (delivered replies, outbox, approval requests, status changes), but it does not say whether the reset is irreversible, what permissions are required, or whether any other demo state is affected.

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 definition is a single efficient sentence with the action and affected state front-loaded. Every listed item earns its place by clarifying the reset scope.

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 zero-parameter reset tool with no output schema, the description covers the main effects but omits important behavioral context such as irreversibility and required permissions. With no annotations supplied, it should do more to warn an agent before a destructive reset.

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 tool has zero parameters, so there is no parameter semantics to explain; the baseline for zero-parameter tools is 4. The description appropriately does not waste space on nonexistent inputs.

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 uses the specific verb "Restore" with a clear scope, "all demo state," and enumerates the affected artifacts: delivered replies, outbox, approval requests, and status changes. It is easy to distinguish from sibling read/list tools, though it does not explicitly contrast itself with other mutation tools.

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 does not state when to use this reset versus alternatives, nor does it give prerequisites or exclusions. The destructive nature is implied by "removes" and "clears," but there is no explicit guidance about when this should be invoked.

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