percentage_reset

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

No annotations are provided, so the description bears full responsibility. It states that the tool resets the session to initial state, which implies a destructive action (losing current progress), but does not mention side effects, required permissions, or what happens if no session exists. The description is too minimal for a mutation 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, clear sentence with no redundant words. Every part is necessary and informative for the core action.

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 no output schema and a simple reset action, the description covers the basic purpose. However, it lacks details like whether the session must be initialized first, what 'initial state' means precisely, and any return value or confirmation. It is adequate but leaves gaps.

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 and 100% schema coverage trivially. The description adds value by specifying the reset goes 'to initial state', clarifying the semantic outcome beyond the schema. Baseline 4 for zero-parameter tools is appropriate.

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 'Reset' and the resource 'Percentage betting session', and specifies the outcome 'to initial state'. It uniquely identifies this tool among siblings (e.g., cocomo_reset, fibonacci_reset) by referencing the 'Percentage' strategy.

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 usage for resetting a Percentage session, but does not explicitly state when to use this tool versus alternatives (e.g., re-initializing), prerequisites (e.g., an active session), or when not to use it. The context from sibling names helps but the description provides no direct guidance.

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