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

The description discloses concrete behavioral details beyond the annotations: it resets the hop chain and turn quota, requires thread membership, and has a cooldown after a freeze. These are meaningful side effects and access constraints that an agent needs to know.

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 compact and front-loaded with the core purpose, followed by three terse, informative sentences. Every sentence adds distinct value: effect, quota reset, membership restriction, and cooldown.

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 low-complexity tool with two documented parameters and no output schema, the description covers the action, side effects, access, and timing. The 'short cooldown' is somewhat vague, but not enough to leave the agent without necessary context.

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 100%, so both parameters are already documented in the input schema. The description adds no extra parameter-level detail, which is acceptable since the schema fully covers parameter meaning.

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 identifies the action ('Reopen'), the resource ('a frozen thread'), and the specific effects ('Resets the hop chain and the turn quota'). This goes beyond the title's verb and leaves no ambiguity about what the tool does.

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 gives useful context for when the tool is applicable: only 'Thread members' can use it, and a 'Short cooldown after a freeze' implies timing constraints. It doesn't name alternative tools, but no direct sibling alternative for unfreezing appears in the sibling list.

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