delete_component

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. Beyond that, the description adds only vague marketing-style phrasing ("independent native SOLIDWORKS engine", "Inspect verified measurements and error evidence") without stating what happens to mated/dependent geometry, whether the deletion is reversible, or what the response contains.

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 opening clause is well front-loaded, but the remaining two sentences are boilerplate: unit conventions (mm/degrees/kg) are irrelevant to a deletion, and "inspect verified measurements and error evidence" is unfalsifiable filler that consumes attention without informing the call.

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 with one fully undocumented parameter and no output schema, the description omits the essential context: valid identifier forms, behavior on failure, and impact on assemblies or mates referencing the component. An agent cannot call this correctly without trial and error.

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 0% and the single required parameter "component" is a bare string with no enum or format. The description says nothing about how a component is identified (name, index, path, or handle), so it fails to compensate for the coverage 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?

"Delete component" is a specific verb+resource pair that names exactly the operation performed. It does not, however, distinguish this from nearby siblings such as delete_feature, delete_mate, or delete_equation, nor explain what constitutes a 'component' in this domain.

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 versus delete_feature or replace_component, no prerequisites, and no warning about irreversible removal of a component from a document. The agent must infer all usage conditions from the name alone.

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