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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered structurally. The description adds a useful conversational-permission constraint, but says nothing about what is destroyed (component alone or its dependents) or whether deletion is recoverable—context that matters for a non-idempotent destructive tool.

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?

Two short sentences, no waste, with the destructive guardrail front-loaded right after the action statement. Every sentence earns its place.

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?

Annotations carry the destructive safety profile and there is no output schema to explain, so the definition is minimally callable. However, for a destructive mutation with fully undocumented parameters and no disclosure of deletion scope, it is only adequately complete rather than thorough.

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% for both required parameters (slug, component_id), and the description gives no indication of what they identify or their expected format. The description does nothing to compensate for the undocumented parameters, leaving the agent to guess.

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?

States a specific verb and resource ("Delete a component"), clearly distinguishing it from sibling deletes like delete_check and delete_status_page. It stops short of explicitly naming alternatives, but the target object 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?

"Run only when the user asked to delete this component in this conversation" gives a concrete when-to-use guardrail that constrains destructive invocation. It doesn't mention alternatives such as update_component or manage_component_group that might achieve a user's intent without deletion.

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