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

While annotations cover the destructive nature, the description adds vital context regarding the operational state (stuck/timeout) that necessitates this action. This conditional context is extremely helpful for the agent's decision-making process.

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 highly concise and efficient. It front-loads the primary function and immediately follows with the necessary operational constraints, adding zero filler.

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 destructive, zero-parameter tool, the definition is maximally complete. The usage guidelines fully cover the agent's decision-making pathway, making the invocation highly safe.

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?

Since the input schema is empty (0 parameters), the baseline score applies. The description is perfectly suited for an empty-parameter tool.

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 uses a specific verb ('Force-stop') and identifies the resource being acted upon ('Anon processing of the current ask_anon request'). This immediately distinguishes it from related tools like 'ask_anon' or 'anon_message'.

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?

It provides explicit, critical instructions on when to use the tool and when not to. The agent is guided to only use it when 'isProcessing stays true for too long or the request is stuck,' and to use polling otherwise.

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