delete_component

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

Annotations already flag this as destructive (destructiveHint=true, readOnlyHint=false), so the safety profile is partly covered. However, the description adds nothing beyond that: it never says the deletion is irreversible, what happens to issues referencing the component, or that the `confirm` flag is required to proceed.

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?

A single front-loaded sentence with no wasted words. It is efficient, though for a destructive operation the terseness shades into under-specification rather than optimal brevity.

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 no output schema and an undocumented `confirm` parameter, the description should warn about irreversibility and describe the confirmation requirement. As written it leaves the agent without the information needed to invoke the tool safely.

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 50% – `confirm` is documented in the schema while `componentId` is not. The description's 'by id' loosely maps to componentId, but it does not explain the id type or the role of `confirm`, so it adds only marginal value over the schema.

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 (component) and clarifies the identifier mechanism ('by id'), which lets an agent distinguish it from get_component, update_component and create_component. It offers no further scoping, but the verb+resource pairing is unambiguous.

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 when-to-use guidance, no mention of alternatives such as update_component, and no stated prerequisites or cautions. An agent must infer everything about when deletion is the right call.

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