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

Annotations only say non-read-only and destructive; the description goes far beyond by disclosing that the list fully replaces existing assignees, that each add/remove posts a visible notification message to the ticket thread, that on a public ticket the audience is every beta tester, that tokens are single-use and short-lived, and that stale previews fail. This is exactly the kind of side-effect and auth-context detail an agent needs before a destructive mutation.

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 mutation semantics, then constraints, then the two-step protocol — a sensible ordering for a destructive tool. It is dense and long, but nearly every sentence carries an operational constraint; the closing note about the 'name' field is the one sentence that could be trimmed.

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 destructive, token-gated mutation with no output schema, the description covers replacement semantics, id sourcing, eligibility constraints, notification side effects, failure/re-preview behavior, and token lifetime. Nothing an agent needs to call it safely and correctly is missing.

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 100% and the schema already documents replacement semantics, the manager-only source, and the confirmationToken flow, so the description mostly restates rather than extends it. The only marginal addition is the note about the response 'name' field being a display handle, which is not a parameter at all. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Sets who is assigned to a ticket') and immediately clarifies the replace-not-append semantics, which distinguishes it from the addBetaManager/removeBetaManager siblings. An agent knows exactly what state change this produces 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?

Explicitly names the prerequisite source for ids (listBetaManagers), states the manager-only constraint, states the chat-ticket exclusion, and lays out the full two-step call protocol with the exact condition for the second call (user explicitly approves, same arguments plus token). It even covers the concurrency case where the confirm fails and the agent must re-preview.

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