Delete BIM Level

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

The description reinforces the annotations' destructiveHint with 'cannot be undone' and adds context about the association requirement. It does not contradict annotations and provides useful behavioral context beyond what annotations offer.

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 contains redundancy (e.g., 'permanently delete' and 'Permanently removes' repeated) and includes extraneous API endpoint details. Could be more concise while retaining key information.

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 delete tool without an output schema, the description adequately covers the precondition (no published model associations) and irreversibility. It lacks information on error handling if the precondition fails, but overall is sufficient.

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% with clear parameter descriptions. The description merely restates that id and project_id are required, adding no new semantics. Baseline 3 is appropriate.

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 tool deletes a BIM Level, specifies the condition for deletion (not associated with published models), and emphasizes the permanent nature. It distinguishes from sibling tools (e.g., create, update, list) by its delete focus.

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 indicates when to use the tool (to permanently delete a BIM Level) and provides a precondition (no published model associations). However, it does not explicitly state when not to use it or list alternatives, though sibling tools provide implicit choices.

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