subscription_groups_delete_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the deletion is permanent or reversible, not what related resources (localizations, subscriptions, versions) are cascaded, and not what permissions are required. A destructive operation documented only by its HTTP route leaves the agent with no behavioral context.

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 and front-loaded, but the parenthetical duplicate of the same endpoint string earns nothing and indicates a mechanical template rather than deliberate structuring of 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?

For a destructive, annotation-free tool with no output schema, the description should at minimum state permanence and side effects. As written, an agent can technically call it with the required id but has no basis to judge consequences before invoking it.

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?

With a single parameter and 100% schema description coverage, the schema already documents the required 'id'. The description adds no format hints (e.g. whether id is an opaque resource ID) beyond what the schema provides, so the baseline 3 applies.

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 states a verb and resource ('DELETE /v1/subscriptionGroups/{id}'), so the action and target are identifiable. However, it adds nothing beyond the tool name and simply restates the name in a duplicated parenthetical, giving no differentiation from the many sibling *_delete_instance tools.

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 guidance on when to use this tool versus alternatives such as subscription_groups_update_instance or subscription_groups_get_instance. Deletion intent is implied only by the word DELETE; no prerequisites, exclusions, or conditions are stated.

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