harbor_labels

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

The readOnlyHint annotation already tells the agent this is a safe read, so the "[READ]" tag adds nothing. "Measured truncation" hints that results may be capped and reported, but it does not say how truncation is signalled, what the default window is, or how to retrieve the rest.

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?

It is a single short sentence with the operation front-loaded, which is efficient. But the brevity is achieved by dropping necessary information, and "measured truncation" is an obscure phrase that costs comprehension rather than saving it.

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?

There is no output schema, minimal annotation coverage, and two undocumented parameters with defaults, so the description must carry most of the load and does not. It leaves undefined what a label record contains, what `target` scopes to, and how truncation is surfaced to the caller.

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%, and the description mentions neither `limit` nor `target`. An agent gets no guidance on the default page size of 50, on what values `target` accepts, or on how the two interact, so the parameter burden is entirely unaddressed.

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?

"List Harbor labels" names a specific verb and resource, so the basic operation is identifiable. However, the trailing phrase "with measured truncation" is unexplained jargon, and nothing distinguishes this from sibling listing tools such as harbor_tags or harbor_artifacts.

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 only usage signal is the "[READ]" prefix, which merely restates the readOnly annotation. There is no statement of when to call this instead of harbor_tags, harbor_artifacts, or the other listing siblings, and no prerequisites or scope conditions are given.

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