sentinel_reset_demo

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

No annotations are provided, so the description carries the behavioral burden. 'Reset all mock servers to their original, clean state' conveys a destructive/state-changing operation and indicates what gets affected (all servers, restoring to original state). However, it doesn't disclose whether this is irreversible, whether it clears policies/rules added, or what the outcome/return looks like. It's adequately transparent for the reset action itself but lacks detail about what exactly is destroyed.

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?

Single sentence, front-loaded with the action ('Reset'), zero waste. Every word earns its place. No filler or redundancy.

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 essential need: what it does and when to use it. It could add a note about whether review queues, call history, or ledger data are also cleared, but for the primary purpose of resetting mock servers, it's reasonably complete.

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 0 parameters, so there's nothing for the description to document. With zero parameters, a baseline of 4 is appropriate per the rubric. The description doesn't need to add parameter semantics since the schema is complete at 100% coverage.

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 clearly states the verb+resource: 'Reset all mock servers to their original, clean state after running attack simulations.' It distinguishes this from siblings like sentinel_setup_demo (which sets up the demo) and sentinel_run_full_demo. However, it doesn't explicitly contrast with sentinel_setup_demo, which could be confused as similar reset-type operations.

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 phrase 'after running attack simulations' gives clear context for when this tool should be used. It implies the workflow is run attack → reset. It doesn't explicitly name alternatives or exclusions, but the usage window is reasonably specified for a no-parameter reset tool.

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