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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds only the subscriber precondition and does not disclose that changes are destructive, idempotent, or how omitted irritants behave — that detail lives in the schema, not the description. No contradiction with annotations.

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?

A single tight sentence with the audience qualifier front-loaded and no filler. It is efficient, though it is arguably too sparse to be maximally useful.

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?

An output schema and rich annotations exist, so return values and safety are not the description's burden. Still, for a nested-object, destructive, subscriber-gated mutation, the description leaves gaps: no mention of the destructive nature, no clarification of the undocumented lang parameter.

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 description reinforces that levels are per-irritant and define a hiding threshold, which adds meaning over the raw enum of integers. But with schema description coverage at 50%, the 'lang' parameter's purpose is left entirely unexplained in both schema and description, so compensation is only partial.

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 names a specific verb (set) and resource (irritant levels / hidden thresholds per irritant), and 'Subscribers:' scopes who it applies to, which separates it from rating or taste-profile siblings. It stops short of distinguishing itself explicitly from tools like rate_title, but the resource is concrete enough to identify the operation.

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?

'Subscribers:' implies a precondition (subscription required) and the schema note about 0 disabling an irritant and omitted keys remaining unchanged clarifies partial-update usage. However, the description never states when an agent should call this versus related siblings, and no when-not guidance is given.

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