harbor_statistics

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

The readOnlyHint annotation already establishes this is a non-mutating call, and the "[READ]" prefix reinforces rather than contradicts that. The description adds the registry-wide aggregation scope, which is useful behavioral context, but says nothing about what the response contains (fields, format, whether counts are filtered) and there is no output schema to cover that.

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 front-loaded sentence with a scope qualifier and zero filler; the [READ] tag is arguably redundant given the annotation, but it does not bloat the text. It is efficient, though its brevity comes partly from omitting needed information rather than from tight editing.

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 tool with no output schema, the description should at least sketch what counts are returned, and it should explain the undocumented "target" parameter. Neither is covered, so an agent cannot tell what "target" filters or what shape the return takes.

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?

There is one parameter, "target", with 0% schema description coverage, so the description is the only place its meaning could be established — yet "target" is never mentioned. With a single optional parameter and no output schema, this is the one detail the agent needs and it is absent.

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 registry-wide project and repository counts" names a specific verb (get) and resource (project/repository counts) and states the scope (registry-wide), which distinguishes it from listing siblings like harbor_projects and harbor_repositories. The purpose is clear without opening the schema, though the phrasing is terse.

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?

Usage is only implied: "registry-wide" suggests this is the aggregate/summary call rather than a per-project listing, so an agent can infer it should be preferred when only totals are needed. However, no sibling is named and there is no explicit when-not-to-use guidance versus harbor_projects, harbor_repositories, or harbor_project_summary.

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