vibemk_bulk_delete_service_groups

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

The word 'Delete' implies destruction, but there are no annotations to cover safety, and the description does not disclose whether deletion is permanent, irreversible, or whether it affects associated rules or configurations. Since no annotations exist, the description carries the responsibility and does not fully disclose side effects.

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?

The description is extremely concise, using a single sentence that captures the action and scope. No unnecessary words or filler. The title-like prefix 'Bulk delete service groups' is redundant but harmless, and overall structure is lean.

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 simple bulk deletion operation, the description covers the essential information: what is being deleted, the plural nature, and the parameter. It does not describe error handling, partial success behavior, or return values, but given the simplicity and lack of an output schema, it is adequately complete for an agent to understand the operation.

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?

The only parameter 'entries' is described as 'List of service group names to delete', which directly explains its purpose and matches the schema's array-of-strings type. This provides clear meaning beyond the raw type, but there is no additional detail about constraints, formatting, or existence requirements.

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 clearly states the action ('Delete') and the target resource ('service groups'), and the inclusion of 'multiple' and 'Bulk' in the name and description differentiates it from the singular 'delete_service_group' sibling. The purpose is immediately obvious.

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 description says 'Delete multiple service groups at once', which implies it is meant for batch deletion, but it does not explicitly contrast with using the singular 'delete_service_group' or mention when one would prefer this bulk variant. Guidance is implied rather than explicit.

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