Удаление дополнения из кластера

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

The description claims the action is irreversible, which directly contradicts the annotation destructiveHint=false. This is a serious inconsistency that could mislead an agent about the tool's safety profile, warranting the lowest score.

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 two sentences long, immediately states the purpose, and includes the critical side effect (irreversibility) without any wasted words.

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?

The description covers the basic purpose and side effect for a simple 2-parameter tool, but the contradiction with annotations undermines completeness by leaving the agent uncertain about the destructive nature. No mention of prerequisites beyond 'previously installed' is a minor gap.

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 100% and both parameters have clear descriptions in the schema. The tool description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 uses the specific verb 'deletes' with the resource 'addon' and context 'cluster', clearly distinguishing it from sibling operations like install, update, or list. The phrase 'previously installed' adds scope and confirms the action is removal.

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?

No guidance is provided about when to use this tool or how it differs from alternatives. The description only states what it does, leaving the agent to infer usage from the tool name and sibling list.

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