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

Despite destructiveHint=true, the description supplies context annotations cannot: changes are confined to this server's own monitor, nothing in TikTok is mutated, and the action never consumes the monthly change limit. It also discloses the mandatory two-call preview/confirm_token flow with a 10-minute token window.

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?

Front-loaded with the core scope statement, then the call pattern, then the operation list. Slightly redundant, since 'nothing in TikTok changes' appears twice and the monthly-limit exclusion is stated in two places, but the density of useful information is high.

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 output schema, the description still explains the two-phase response (preview plus confirm_token, then apply) and the safety boundary, which is everything an agent needs to call this destructive tool correctly.

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 coverage is 100%, so the baseline is 3; the description earns more by explaining that "arguments" carries the operation's fields, the optional "connection" for multi-account setups, and the confirm_token on the second call, plus that tool_name selects the named operation.

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 (deletes this server's TikTok ad-account monitors) and immediately scopes it: 'Nothing in TikTok changes.' The named operation tiktok_delete_monitor is described concretely as stopping checks and email, which distinguishes it from the read/create/update siblings.

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?

Gives explicit invocation form, the rule for passing "connection" when multiple ad accounts exist, and pointers to get_tool_schema and tiktok_ads_read {"action":"list_tools"} for discovering operations. It does not explicitly say when to prefer tiktok_ads_update over delete, but the operational context is otherwise unambiguous.

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