harbor_volumes

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

Annotations already declare readOnlyHint=true, so the safety profile needs no restating. The description adds modest value by revealing the source endpoint (system-info), which hints at the data's nature, but says nothing about return shape, freshness, or failure behavior when the endpoint is unavailable.

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?

One sentence, front-loaded with the read tag and the resource, with no filler. It is efficient; the terseness is a completeness problem rather than a verbosity problem.

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?

No output schema exists and the sole parameter is undocumented, so the description is the only place that could explain the return payload and the target argument — and it does neither. For a tool an agent must call blind, this is under-specified.

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 single optional "target" parameter has 0% schema description coverage and the description never mentions it at all. An agent has no way to know what a target is (host, registry instance, storage backend?) or what omitting it does.

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?

"Get Harbor storage volume usage" gives a specific verb plus resource, and naming the system-info endpoint makes the data source concrete. It is distinguishable from most siblings (e.g. harbor_health, harbor_statistics, harbor_quotas), though the description never explicitly states how it differs from those overlapping usage/quota tools.

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 "[READ]" tag implies a safe retrieval operation but no when-to-use guidance is given. With harbor_statistics, harbor_quotas and harbor_health in the sibling list, an agent gets no signal about which to pick for storage-usage questions.

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