freeze_clear

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

With only readOnlyHint=false available, the description does real work by disclosing that omitting the address destroys ALL freezes — an agent needs that scope warning to avoid accidental mass mutation. It still omits reversibility, permissions, and any indication of what a successful clear returns.

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?

One compact sentence pair with zero filler; the core action leads and the branching behavior follows immediately. 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 single-optional-parameter mutation with no output schema, the description covers the action and both branches completely. Only the destructive-scope caveat could be expanded (e.g., that the clear-all is irreversible), which keeps it short of a 5.

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 coverage is 100% and the single parameter's own description already says "Omit to clear all." The description restates this rather than adding format, type, or range detail beyond the schema, so the baseline of 3 applies.

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?

"Remove a freeze" states a specific verb and resource, and the paired parameter guidance makes the operation unambiguous. It never names freeze_set or freeze_list, so the agent distinguishes it from siblings only via the tool name rather than explicit description text.

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 clearly explains the two operating modes (targeted removal vs. clearing everything), which implies when to pick each. It offers no guidance on when this tool is preferred over related tools such as freeze_list, and no prerequisites are stated.

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