harbor_quotas

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

readOnlyHint=true already establishes the safety profile, and the '[READ]' prefix merely restates it, adding no new behavioral context. Nothing is said about quota semantics (hard vs. soft limits, what a returned usage number means) or how results are paged given the defaulted limit.

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?

A single short sentence with no filler and the verb front-loaded. It is efficient rather than verbose; the problem is under-specification, which is penalized in other dimensions, not padding.

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?

With no output schema, no annotation coverage beyond readOnlyHint, and two fully undocumented parameters, the description leaves too much unresolved for an agent to call it confidently. At minimum it should define what 'target' scopes to and what the response contains.

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 0%, so the description carries the full burden but explains neither parameter. 'target' in particular is opaque — it could be a project, registry, or repository — and the defaulted 'limit' of 50 is never acknowledged, so the agent cannot infer scoping or result size.

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?

States a specific verb ('List') and resource ('registry quota usage and limits'), and the '[READ]' prefix marks it as non-mutating. None of the listed siblings deal with quotas, so an agent can place it without confusion, though the description never explicitly contrasts it with project- or repository-scoped siblings.

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 this is a safe lookup call, which weakly implies when to use it. There is no statement of when to prefer this over harbor_project, harbor_projects, or harbor_statistics, and no mention of prerequisites such as needing a project context.

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