catia_delete_relation

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

The description only restates the destructive action already declared by annotations (destructiveHint=true). It does not disclose additional behavioral traits such as cascading effects on dependent formulas, irreversibility beyond the annotation, or any required permissions. With annotations covering the destructive hint, the description adds no extra 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?

The description is a single, compact sentence that front-loads the action ('Delete') and immediately clarifies the scope. Every word earns its place, with no fluff or redundancy.

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 single-parameter destructive tool, the description covers the essential action and target. However, it omits any usage context (e.g., when deletion is appropriate) and does not elaborate on side effects beyond the annotation, which might be expected for a destructive operation. It is adequate but not rich.

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 schema provides 100% coverage for the single 'name' parameter with the description 'Relation name.' The tool description does not add any further semantics or constraints beyond what the schema already states, so it meets the baseline without improvement.

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 clear action (delete) and a specific resource (relation) with enumerated types (formula, rule, check, design table). This distinguishes it from sibling deletion tools like catia_delete_parameter and catia_delete_element, which target different entities.

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?

No guidance is given on when to use this tool versus alternatives such as catia_set_relation_active or catia_list_relations. There is no mention of prerequisites, exclusions, or context about the relation lifecycle, leaving the agent to infer appropriate usage.

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