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

Annotations already cover the safety profile (readOnlyHint, idempotentHint), so the description doesn't need to restate them; instead it adds the workflow constraint of checking before a subsequent ask_anon call and states the return shape ('isProcessing: true|false'), which matters since there is no output schema. It doesn't discuss polling frequency or timing/expiry behavior of the processing state, so it stops short of a 5.

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?

Three compact sentences with the core purpose front-loaded, followed by the return value and then the usage conditions. No filler or redundant restatement of the name.

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-param, read-only status check with no output schema, the description supplies the missing return contract and the routing to abort. Minor gaps remain around whether the state can persist or time out, which an agent might want when deciding how long to wait.

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 to document; schema coverage is 100% by definition. Baseline 4 applies for a no-argument tool, with no parameter behavior left ambiguous.

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 specific verb and resource — checking whether Anon is still processing a prior ask_anon request — and explicitly names the sibling tool (ask_anon) whose state it reports on. It is distinguishable from every other sibling at a glance.

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 gives both when-to-use conditions: before sending another message, and when a request appears stuck. It also names the follow-up tool (abort) for the stuck case, so the agent knows exactly what to do with each outcome.

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