delete_beta_tester

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

Annotations only supply destructiveHint=true; the description adds the critical operational detail that the removal is permanent and that confirmation is mandatory, then specifies the two execution paths (native prompt vs. preview + confirmToken round-trip) and points to MCP_CONFIRM_MODE. This is exactly the behavioral context an agent needs before invoking a destructive tool.

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?

Two sentences, both earning their place: the destructive action and its permanence come first, then the confirmation mechanics. No filler or restated field labels.

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 covers everything an agent needs for a destructive operation: permanence, the mandatory confirmation gate, both confirmation modes, and token provenance. Nothing essential to a correct call 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%, so the baseline is 3, but the description adds state-machine meaning the schema alone doesn't convey: phase 1 returns a preview and confirmToken, and only a repeat call carrying that token proceeds. That sequencing context materially clarifies when confirmToken is legally supplied.

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?

Specific verb+resource ('Permanently remove a beta tester') with an explicit scope qualifier, 'from your team', which distinguishes it from the sibling remove_testers_from_beta_group. An agent can tell what this deletes and at what level 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?

The 'from your team' scope implies this is team-level removal rather than group-level, but the description never names remove_testers_from_beta_group or states when to pick one over the other. It describes the confirmation workflow in detail but leaves alternative selection to inference.

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