delete_feature

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the deletion is permanent, whether permission is required, whether dependent features are affected, or what happens to the model afterward. 'Delete' implies destruction but the description adds no practical 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 clear sentence with no filler and places the core action first. It is concise, though it could have used the available space to add sibling differentiation or behavioral notes without much cost.

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 mutation tool with no annotations, no output schema, and a closely related sibling 'delete_feature_by_name', this description is under-specified. It does not explain how featureId relates to the deletion workflow, warn about irreversibility, or distinguish this tool from its sibling, leaving important context to inference.

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 description coverage is 100%, so the input schema already documents all five parameters, including the elementType enum. The description adds little parameter-level meaning beyond confirming the target is a Part Studio or Assembly, which is the baseline expectation given complete schema coverage.

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 specific verb ('Delete') and resource ('a feature from a Part Studio or Assembly'), making the core operation clear. However, it does not differentiate this tool from the sibling 'delete_feature_by_name', so an agent must inspect the schema to know that this variant deletes by feature ID.

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?

There is no guidance on when to use this tool versus 'delete_feature_by_name' or any other alternative. The description only implies the target context (Part Studio or Assembly), but does not state prerequisites, exclusions, or conditions favoring a sibling tool.

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