delete_website_group

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known; the description adds the write-permission requirement, which is useful. However, it does not disclose whether deleting the group also deletes contained websites or whether the action is reversible, so behavioral context is only partially enriched.

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 a single sentence that states the operation, target, and permission requirement without filler. Every element earns its place and the core action is front-loaded.

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 one-parameter destructive operation with annotations covering read-only and destructive hints, the description is largely complete: it names the target, the required permission, and the operation. The only gap is side-effect detail (cascade deletion or reversibility), which is not essential for basic invocation but would help an agent reason about consequences.

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 input schema already covers the only parameter (group_id) with 100% coverage and a clear description ('Group ID to delete'). The tool description adds no parameter-level meaning, so the baseline score of 3 is appropriate because the schema does the heavy lifting.

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 uses a specific verb ('Delete') and resource ('website group') plus the system context ('from LogicMonitor'), making the tool's purpose unambiguous. It naturally differentiates from sibling tools like create_website_group and get_website_groups by the delete operation.

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 does not state when to use this tool over alternatives, mention prerequisites beyond write permission, or call out sibling deletion tools (e.g., delete_device_group, delete_recipient_group). An agent has to infer selection from the name and schema alone.

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