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

The description adds behavioral context beyond the annotations by explaining that the reset applies live when in a room. Annotations already indicate idempotent and non-destructive, and the description's 'Reset' is consistent with the mutation implied by readOnlyHint=false. No contradiction.

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?

Two short sentences carry all the essential information without redundancy. The main action is front-loaded, and the live-application note is placed as a concise secondary point. No unnecessary words.

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 parameterless reset tool, the description is complete: it specifies what is reset, to what defaults, and the live behavior. Annotations cover the idempotent and non-destructive profile, and no output schema exists, so return-value documentation is not required.

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 schema coverage is 100%, so there is nothing for the description to explain parameter-wise. The description stays appropriately focused on behavior rather than inventing unnecessary parameter detail.

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 clear verb ('Reset') and the exact resources affected ('look, persona and voice'), plus the target state ('plain defaults'). This distinguishes it from siblings like change_style and set_defaults, which imply different operations.

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: use this when you want to revert to defaults. It adds a useful condition ('Applies live if you're in a room') but does not explicitly contrast with alternatives like set_defaults or change_style, leaving the when-not-to-use somewhat implicit.

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