deleteAgentVersion

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

The description says 'Delete a saved version,' which is a destructive action, but annotations declare destructiveHint=false. This is a direct contradiction that misleads the agent about the tool's safety profile. No other behavioral context is provided.

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 short and to the point, but it lacks any structural aid like examples or caveats. The '(Tags: Agents)' is extraneous, and the one-liner is minimal but not particularly well-crafted for an agent's needs.

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 destructive delete operation, the description omits critical information such as whether deletion is permanent, side effects, or permission requirements. The schema covers parameters, but the behavioral context is severely lacking, especially given the annotation contradiction.

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?

Both parameters (agent_id and version_number) are fully described in the schema with 100% coverage, so the description adds no additional meaning. The baseline of 3 is appropriate because the schema handles parameter semantics adequately.

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 verb 'Delete' and the resource 'a saved version,' which distinguishes it from sibling tools like restoreAgentVersion, renameAgentVersion, and createAgentVersion. The purpose is unambiguous and specific.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, use cases, or contrast with related version management tools, leaving the agent without contextual decision support.

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