beta_groups_delete_instance

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

With no annotations provided, the description carries the full behavioral burden and delivers none of it. It does not state that the operation is destructive and irreversible, whether it cascades to related beta testers/builds, what permissions are required, or whether the group must be empty first.

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?

It is short, but the parenthetical '(DELETE /v1/betaGroups/{id})' is a pure duplication of the preceding text and earns nothing. Brevity here comes from omission, not from efficient communication.

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?

A destructive delete with no annotations, no output schema, and no error semantics should explain consequences, permissions, and failure modes. The description supplies none of this, leaving an agent unable to judge whether the call is safe or what happens on success or failure.

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 single parameter 'id' is documented in the schema as 'the id of the requested resource'. The description adds nothing beyond echoing '{id}' in the path, so the baseline 3 applies when the schema does all the work.

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 is a raw HTTP route signature, 'DELETE /v1/betaGroups/{id}', duplicated verbatim in parentheses. It technically conveys the verb and resource, but it merely restates the tool name (beta_groups_delete_instance) rather than stating the purpose in plain language, and it does nothing to distinguish this from the dozens of other *_delete_instance 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as beta_groups_get_instance or beta_groups_update_instance. The only usage signal is the implicit 'this deletes' from the endpoint verb, which the agent could infer from the name alone.

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