delete_version

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

The description only says 'Delete', indicating a mutation, but does not disclose any additional behavioral traits such as irreversibility, cascading effects, or required permissions. With no annotations provided, this minimal disclosure is insufficient.

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 very concise, front-loaded with the tool's purpose, and includes two specific use cases. Every sentence adds value with no unnecessary content.

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 simple delete operation with 3 parameters and no output schema, the description covers the main purpose and use cases. It could mention permanence or prerequisites, but overall it is adequate.

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?

Since the input schema has 100% coverage with descriptive parameter comments, the description does not add extra meaning beyond what the schema provides. Baseline 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 clearly states the action 'Delete' and the resource 'version' within a specific context 'Yunxiao Project'. It includes use cases that help differentiate from sibling tools like create_version or update_version.

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 provides clear use cases ('Remove obsolete versions', 'Clean up project versions') which imply appropriate contexts for use. However, it does not explicitly state when not to use the tool or mention alternatives.

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