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 burden. While it mentions 'in-memory' and 'deterministic seed state,' it does not disclose the destructive nature of a reset (overwriting current state), the scope of the reset (e.g., per principalId), or any side effects. This is a significant gap for a reset-type tool.

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 a single, concise sentence that immediately conveys the core function. It is well-front-loaded and contains no extraneous words.

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?

Despite the simplicity of the tool (one parameter, no nested objects), the description leaves key gaps: it does not explain the purpose of 'principalId' and does not describe the behavioral outcomes beyond 'deterministic seed state.' An output schema exists, but the missing parameter semantics and side-effect disclosure make the description incomplete for an agent to invoke this correctly.

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 description coverage is 0%. The description does not mention the required 'principalId' parameter at all, nor does it explain its meaning or role in the reset operation. The schema only shows it as a string with minLength 1, leaving the agent to infer its purpose.

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 function: 'Reset the in-memory demo workflows and subscriptions to their deterministic seed state.' The verb 'reset' and the specific resource ('in-memory demo workflows and subscriptions') are precise, and this distinguishes it from sibling tools like simulate_resolution or rollback_action, which do not reset state.

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 implies this tool is for resetting demo state, but it does not explicitly state when to use it instead of alternatives (e.g., rollback_action) or provide any exclusions. The usage is implicit from the name and description, but no direct guidance is given.

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