df_delete_dimension_group

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

The description goes beyond annotations by disclosing the permanent nature of the deletion (destructiveHint only says destructive, not permanent) and the specific rejection condition when assigned to a fact table. This adds valuable context that annotations do not capture. Idempotency is annotated but not described, which is acceptable.

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 two sentences with the critical warning front-loaded and no unnecessary words. It is efficient and well-structured for quick comprehension.

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?

The description covers the essential aspects: permanent deletion and the assignment constraint. It does not mention return values or error handling, but for a delete operation without an output schema, that is often implicit. It is reasonably complete for an agent to call correctly.

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 67% with descriptions for project_id and version_id, but dimension_group_id lacks a description. The tool description adds no parameter details, so it does not compensate for the missing schema description. However, the parameter is self-explanatory from its name, and the schema covers most parameters, making this a moderate gap.

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 verb 'Delete' and resource 'dimension group', distinguishing it from sibling tools like df_delete_measure and df_delete_dimension. It also adds permanent-deletion scope and a rejection condition when assigned to a fact table, making the purpose unambiguous.

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 provides the key context that the operation is permanent and is rejected while the group is assigned to a fact table, implying a prerequisite to unassign first. However, it does not explicitly name alternative tools or state when to use this over other delete operations, though the name itself is sufficiently specific.

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