ateam_delete_skill

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

With no annotations, the description fully covers behavioral effects: kills MCP process, unregisters from skill registry, deletes from Mongo, removes from solution arrays, deletes files from Builder FS. This fully informs the agent of the destructive nature and side effects.

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 three sentences: clear purpose, detailed effects, and closing usage guidance. No redundant words, and every sentence adds value.

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 number of sibling tools and the complexity of the operation, the description is complete. It explains what, how, and when to use, without needing an output schema for a delete operation.

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%, so the schema already documents both parameters. The description adds no extra meaning beyond what the schema provides, meeting the baseline for high coverage.

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 clearly states 'Delete a single skill from a deployed solution,' specifying the verb and resource. It distinguishes from sibling delete tools like ateam_delete_connector and ateam_delete_solution by clarifying it targets a single skill within a solution.

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 implicitly provides usage context with 'Use this to drop a skill without tearing down the whole solution,' indicating when this tool is appropriate. However, it does not explicitly mention alternatives or cases where it should not be used, relative to other sibling tools.

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