emotion_reset

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

No annotations are provided, so the description carries the full burden. It states the action ('reset to initial state') but does not disclose side effects, whether the operation is destructive, required permissions, irreversibility, or what 'initial state' specifically means. For a mutation tool, this is a significant lack of behavioral detail.

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 that is front-loaded with the action. Every word contributes meaning without redundancy, making it highly concise and well-structured.

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?

The tool is simple with one required parameter and no output schema, so the description is minimally adequate. However, it lacks contextual information about what 'initial state' constitutes, when to invoke this tool, and what side effects to expect, which would help the agent use it correctly.

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 description coverage is 100%, with user_id documented as '要重置的用户 uid'. The tool description adds no additional meaning about the parameter beyond what the schema already provides. Baseline of 3 is appropriate when the schema fully documents 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 a specific action (reset) on a specific resource (specified user's emotion values) with a clear target state (initial). It distinguishes from sibling emotion_reset_all by emphasizing 'specified user', and from emotion_set by focusing on resetting rather than setting arbitrary values.

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 context: it is for resetting a single user's emotions. However, it does not explicitly state when to use this tool versus alternatives like emotion_reset_all (reset all users) or emotion_set (set specific values), nor does it mention any exclusions or prerequisites.

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