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

Beyond the destructiveHint annotation, the description enumerates exactly which visit statistics are reset (opens, uniques, daily, sources, devices, browsers, countries, log), states that answers are untouched, confirms irreversibility, and explains that new visits count normally afterward. This is rich behavioral context that the annotations alone do not supply.

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 front-loaded with the reset action and remains tightly structured: scope of reset, untouched data, alternative, irreversibility/confirm, and post-reset behavior. Every sentence contributes useful information.

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?

For a destructive reset tool with no output schema, it covers the essential context: what is destroyed, what is preserved, how to delete answers instead, the mandatory confirmation, and how future visits behave. Nothing critical is missing.

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 schema already documents both parameters at 100% coverage, including that confirm must be true and quiz_id is the quiz ID. The description reinforces the confirm requirement but does not add new semantics beyond 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 opens with a specific verb and resource — resetting a quiz's visits — and immediately scopes it to visit statistics. It also distinguishes the tool from delete_quiz_answers, so an agent can tell which sibling handles answer deletion versus visit reset.

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?

It gives a clear alternative for the related but different need of deleting answers ('удалить их — delete_quiz_answers'), effectively stating when not to use this tool. It also flags irreversibility and the mandatory confirm: true, which are essential invocation conditions.

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