Reset customization

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description must carry the rest. It usefully discloses that this is a partial reset that preserves the LowEnd performance flag, a real behavioral nuance. It does not say whether the reset is reversible, whether a backup is needed first, or what happens to settings outside SaveData.Custom.

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?

A single front-loaded sentence naming the target and the preserved exception, with no filler. Every clause 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?

For a zero-parameter mutation with no output schema and readOnlyHint already set false, the description covers what changes and what is preserved. The one gap is reversibility/undo guidance, which matters for a destructive save-data operation.

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 takes zero parameters, so there is nothing for the description to clarify beyond the schema baseline. The description correctly spends no words on 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?

States a specific verb (Reset) and resource (SaveData.Custom) plus the target state (script defaults), and adds a scope exception ('keeps LowEnd performance flag'). It contrasts implicitly with the sibling reanim_set_customization, though it never names the alternative explicitly.

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 name and verb make the use case strongly implied (restore customization to defaults), but the description offers no explicit when-to-use guidance, no contrast with reanim_set_customization, and no pointer to reanim_backup_savedata/reanim_restore_savedata before a destructive reset.

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