reset_session_stats

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

No annotations are provided, so the description fully bears the burden. It clearly states the immediate destructive action ('Zero the session stats counters') and confirms the return value ('confirmation line with the new reset timestamp'). However, it does not discuss permissions or side effects beyond counters.

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 three sentences long, no unnecessary words. It front-loads the core action, provides usage guidance, and ends with the return value. Every sentence earns its place.

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 (no parameters, clear action), the description fully covers purpose, usage, behavior, and return value. The presence of an output schema (not shown) complements the description, but the description alone is sufficient for a correct invocation.

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, so the baseline is 4. No additional parameter description is needed, and the description does not waste space on non-existent parameters.

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 tool's purpose with a specific verb ('Zero') and resource ('session stats counters'). It distinguishes from the sibling 'session_stats' tool by indicating that this tool resets counters while the other likely retrieves them.

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 explicit context for when to use the tool ('at the start of a new Claude session... when the idle-based auto-reset has not fired'). It gives a concrete example (back-to-back sessions), but does not explicitly mention alternatives or when not to use it, leaving room for slight ambiguity.

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