Manage IM sensitive words

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

The annotations already declare destructiveHint: true, and the description adds the important safety requirement that delete and publish must pass confirm: true. It does not describe irreversible effects, permission requirements, or response behavior, but it adds key operational context beyond the 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?

The description is two compact sentences with no wasted text; the action list is front-loaded, and the confirm warning follows directly. It is appropriately sized for a multiplexed action tool.

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 seven-parameter tool with a required action enum, a nested data object, and no output schema or schema descriptions, the definition is too thin. The critical data shape for create/update and the meanings of app, keyword, limit, and offset are absent.

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 0%, so the description must compensate, yet it explains only the action values and the confirm requirement for delete/publish. It leaves app, data, limit, offset, and keyword undocumented, and the nested data object used by create/update is especially opaque.

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 states that the tool manages sensitive words and regex entries, and it enumerates every action supported by the action enum. An agent can identify the resource and the operation set without opening the schema.

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 maps each action to its purpose (list, create, update, delete, fuzzy, publish, thesaurus) and explicitly states that delete and publish require confirm: true. It does not explain when to choose one action over another or describe prerequisites, but the action-level guidance is clear.

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