governor_reset

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It implies a destructive action (reset of history and log) but does not explicitly state consequences, reversibility, or required permissions. The phrase 'empezar una demo limpia' hints at data loss, but lacks clear warnings.

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 extremely concise: two sentences totaling under 20 words, with no redundant phrases. Every part is essential and front-loaded, fulfilling the requirement of being appropriately sized.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is mostly complete. It explains the main action and use case. However, it could be improved by explicitly stating that the reset is irreversible or mentioning the response format.

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 100% (the only parameter 'agentId' has a description in the schema). The tool description adds minimal value beyond that: it mentions that omitting the parameter resets everything, but does not elaborate further. Baseline 3 is appropriate given high schema 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 ('reinicia') and the resources ('historial' and 'registro de decisiones'), specifying a reset/restart action. It distinguishes itself from sibling tools ('governor_evaluate' and 'governor_log') by indicating a different function (reset vs. evaluate/log).

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 a usage scenario ('útil para empezar una demo limpia') which implies when to use it, but it does not explicitly state when not to use it or offer alternatives. Without exclusions or comparisons to siblings, the guidance is implied but incomplete.

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