qa_reset_test_user

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

Since no annotations are provided, the description carries the full burden of disclosing behavioral traits. It says 'Reset', implying a destructive operation, but does not explain what gets reset, whether it wipes data, requires confirmation, or has side effects. The required 'confirm' constant is only visible in the schema, not in the description.

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 concise sentence that front-loads the core action. There is no wasted text, though it lacks supporting details that could make it more helpful.

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 mutation tool with no annotations, no output schema, and zero parameter documentation, this description is insufficient. An agent cannot determine what happens on reset, what 'local fixture control plane' means operationally, or what response to expect.

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 0%, so the description must compensate by explaining the parameters. It does not mention user_id or confirm at all, leaving their meaning and the role of the required 'RESET_TEST_USER' constant entirely to the agent to infer.

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 states a specific verb ('Reset') and resource ('a test user'), and adds the context 'through the opt-in local fixture control plane'. This is clear and distinguishes it from read-only QA tools like qa_get_usage and qa_get_game_state, though it does not explicitly name an alternative.

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?

No guidance is given about when to use this tool versus the sibling mutation tools such as qa_set_subscription, qa_seed_questions, or qa_set_game_level. The phrase 'test user' implies QA use, but there is no explicit context, prerequisites, or exclusion criteria.

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