Storage Content

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

Annotations already signal readOnlyHint=false and destructiveHint=true, so the description adds little behavioral context beyond what is structured. It does not explain that delete permanently removes volumes, prune follows retention rules, upload may overwrite existing content, or that download_url fetches from a remote source.

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 one-line description is compact but under-specified for a tool with six actions and twenty parameters. It lacks any structure separating read operations from destructive ones or grouping action-specific parameters, so the brevity is not earned.

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 complex multi-action tool with no output schema, this description is far from complete. It never explains action-specific required parameters, retention/prune behavior, upload requirements, or what the operation returns, leaving the agent to discover critical details from the schema and action enum alone.

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 description coverage is 95%, so the parameters are largely self-documented. The description contributes no parameter semantics, which matches the baseline, but it also does not help the agent understand which parameters apply to which action.

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 names a specific resource (storage content) and lists six operation verbs, so the agent can tell this is a content-management dispatcher. However, it relies on the broad verb 'Manage' and gives no detail about what each action does, and it does not distinguish the tool from siblings like proxmox_storage_config or proxmox_file_restore.

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 guidance on when to use this tool versus alternatives, nor when to choose one action over another. The action list is implied usage at best, but the description never states conditions, prerequisites, or exclusions.

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