reset_environment

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a destructive-then-restorative pattern ('Reset... and restore'), implying state reversion rather than clearing to factory defaults. However, it fails to specify what exactly gets reset (active captures? settings? sessions?) or whether unsaved work is permanently 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?

The description consists of a single, efficient sentence that frontloads the action verb 'Reset' and immediately qualifies the scope with 'restore the saved configuration.' Every word contributes to understanding the tool's dual-phase behavior without 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?

While the description identifies the general operation, it lacks critical context for a state-resetting tool: it does not specify the scope of the reset, the source of the 'saved configuration,' or warn about destructive side effects. The existence of an output schema reduces the burden to explain return values, but the operational impact remains under-specified.

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 input schema contains zero parameters, establishing a baseline score of 4 per evaluation rules. The description appropriately does not invent parameter semantics where none exist in the schema.

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 specific verbs ('Reset' and 'restore') with the resource 'Charles environment' and distinguishes this state-management tool from traffic-analysis siblings like 'analyze_recorded_traffic' or 'query_live_capture_entries'. However, it assumes familiarity with what constitutes the 'Charles environment' without defining its scope.

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 provides no indication of when to invoke this tool versus alternatives, nor does it warn about potential data loss from resetting active sessions. There is no mention of prerequisites (e.g., whether a configuration must be saved first) or safe usage patterns.

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