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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the description doesn't need to re-state danger. It adds real value on top: the consent requirement ('only when the user asks') and the explicit instruction not to fabricate a target_id. It still doesn't say whether the removal is immediate and what happens to a live stream mid-simulcast.

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 short sentences, purpose first, guardrail second, parameter provenance last. Nothing is redundant and no sentence could be dropped without losing information.

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 an output schema present, return values need not be explained, and the consent rule plus id provenance covers the main preconditions for a destructive two-parameter call. The only gap is the absence of any statement about the effect on the running stream or reversibility beyond the destructive hint.

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 above baseline by giving target_id provenance ('from add_simulcast_target or the stream's simulcast_targets') and a prohibition on inventing it, which is a failure mode the schema cannot express. stream_id receives no comparable treatment.

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 ('Remove a simulcast target') that directly mirrors the tool name and cleanly contrasts with the sibling add_simulcast_target, which it explicitly names. An agent knows exactly which operation this is 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?

'Call this only when the user asks' gives an explicit invocation guardrail that rules out autonomous cleanup of stale targets, which is valuable for a destructive tool. It does not spell out a full when-not/alternative matrix (e.g., use update_live_stream to disable rather than remove), so it falls short of a 5.

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