ateam_delete_solution

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

Discloses destructive behavior: removes the solution from both Skill Builder and A-Team Core. With no annotations provided, this description adequately informs about the irreversible nature and scope of deletion.

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 concise sentences with no waste. Front-loaded with purpose, then adds caution and use case. 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?

For a delete tool, description covers purpose, usage guidance, and behavioral effects. Lacks mention of return value, but no output schema exists. Adequate for the tool's complexity.

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?

Single parameter 'solution_id' with clear schema description. High schema coverage (100%) means description adds no extra meaning beyond what's already in the schema. 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?

Description clearly states it deletes a deployed solution and all its skills from A-Team, specifying the resource and action. It distinguishes from sibling tools like ateam_delete_skill by noting it removes the entire 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?

Explicitly advises caution and states it is useful for cleaning up test solutions or starting fresh. Provides clear context for when to use, though it does not explicitly name alternative tools.

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