delete_group

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

The description labels the tool as DESTRUCTIVE and states it deletes a group, but omits important behavioral details such as permissions required, impact on associated resources, reversibility, or response behavior. Since annotations are absent, the description carries full burden.

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 with one sentence plus a warning, front-loaded effectively. Every word is purposeful.

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 operation with a confirmation mechanism, the description covers the basic action and destructiveness but lacks details on side effects, return values, or the confirmation process beyond what the schema provides. It is adequate but not thorough.

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 coverage is 100%, so baseline is 3. The description adds no extra parameter meaning beyond the schema's descriptions, which already clarify the group_id and the confirmation requirement for schema_file.

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 it deletes a group from a Fivetran account, using a specific verb and resource. However, it does not differentiate from sibling delete tools like delete_connection or delete_destination beyond the resource name.

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 includes a warning to confirm with the user before calling, but provides no guidance on when to use this tool versus alternatives (e.g., delete_user_from_group) or when not to use it.

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