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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is structured data the agent sees. The description adds nothing beyond that: it doesn't say whether the deletion is permanent or recoverable, whether a confirmation or specific permission is required, or what happens to the project's version history afterward. For an irreversible operation, that is a meaningful gap.

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 single short sentence is front-loaded and contains no filler, but its brevity comes from under-specification rather than economy. It is well-formed but does not use its space to convey anything useful.

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?

This is a destructive mutation with no output schema and half its parameters undocumented. An agent needs to know that the target version is permanently removed and how projectId and versionId interact; the description covers none of that, leaving it inadequate for the tool's risk profile.

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 only 50% — projectId is documented inline while versionId has no description in either schema or prose. The description supplies no meaning for versionId (e.g., where it comes from, whether it must belong to the given project), so it fails to compensate for the coverage gap.

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 sentence "Delete a saved version" essentially restates the tool name delete_version with no added specificity about scope (project-level vs. global), which version types are covered, or how it differs from siblings like restore_version, compare_versions, or list_versions. It does convey a verb and resource, but it is tautological rather than descriptive.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent seeing both delete_version and restore_version gets no signal from the description about which is appropriate or whether deletion is the counterpart of restore.

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