uc_volume_delete

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

Annotations already mark the tool as destructive (destructiveHint=true). The description merely states 'Delete', which aligns with annotations but adds no additional behavioral context such as consequences, reversibility, authentication requirements, or whether the operation is idempotent.

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 a single sentence containing the core action and the API endpoint. It is concise and to the point, with no unnecessary wording. However, it could arguably be even shorter by omitting the redundant endpoint.

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 tool's simplicity (1 required parameter, output schema present), the description covers the basic purpose. However, it omits contextual details such as success/failure behavior, whether deletion is soft or hard, or if cascading effects occur.

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?

The input schema has 100% description coverage for the single parameter 'full_name', with clear explanation of its format (catalog.schema.volume). The description does not add any meaning beyond what the schema already provides, so a 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?

The description clearly states the action 'Delete a volume' with the resource type, and the API endpoint is provided. The verb 'delete' is specific and distinct from siblings like uc_volume_create or uc_volume_get, though no explicit differentiation is made.

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 no guidance on when to use this tool versus alternatives (e.g., uc_volume_create, uc_volume_update). It lacks context on necessary prerequisites, such as the volume's existence or required permissions.

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