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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the genuinely useful detail that a reset does not mean 'everything off' but 'all on with Telegram off', which an agent could not derive from structured fields. It does not warn that existing per-switch customizations are overwritten and unrecoverable, which would be the natural complement to destructiveHint.

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?

Two short sentences with zero waste: the effect and its resulting state come first, the usage guard second. Every clause earns its place and nothing is repeated from the title or annotations.

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?

With no parameters, an output schema present, and annotations covering destructiveness and idempotency, the description supplies everything else an agent needs: what the defaults are and when to trigger it. No material gap remains for a zero-argument mutation.

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 no parameter semantics to explain; the baseline of 4 applies. The description correctly conveys that the operation is scoped implicitly to 'the user', clarifying the subject that the empty schema cannot express.

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 and resource ('Put every notification switch ... back to the default') and even enumerates the resulting state ('all on, Telegram off'), which makes the effect unambiguous. It does not explicitly name the sibling it supersedes (notifications.update), so differentiation is implied by scope ('every switch') rather than stated.

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?

Provides an explicit gating condition — 'Only when the user asks to reset them' — which tells the agent not to infer a reset from a partial change request. It stops short of naming the alternative tool (notifications.update) for single-switch edits, leaving that routing to inference.

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