remove_component

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that the operation is mutating and irreversible, details the side effect on controls (component_id cleared but controls kept), and explains the impact on trust-boundary contribution to asset reachability.

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 compact and front-loaded with the core purpose. Each subsequent sentence adds critical information about mutability, side effects, and alternatives without repetition or filler.

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?

Given the output schema exists, return values need no explanation. The description sufficiently covers purpose, irreversibility, side effects, and alternative actions, making the tool's overall behavior clear for an agent selecting and invoking it.

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 already documents model_id and component_id, giving about 67% coverage, but the description does not add further parameter-level detail. The undocumented server_version parameter is not clarified anywhere, leaving a minor semantic 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 opens with a specific verb+resource: 'Remove a component from a threat model.' It clearly distinguishes this from sibling operations by contrasting with asset/attacker removal (no restore counterpart) and explicitly naming edit_component as the alternative for changing a component.

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 gives explicit usage guidance: it is used for removal only, is irreversible, and if the intent is to change rather than remove, the agent should use edit_component. It also draws a comparison to asset/attacker removal to clarify when this tool is and is not appropriate.

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