harbor_artifacts

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

The readOnlyHint annotation already establishes that this is a read operation, and the description's '[READ]' prefix merely repeats that. It adds no behavioral detail such as pagination semantics for the limit parameter, ordering, or whether scan overviews are summarized vs. full vulnerability data.

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 description is a single front-loaded sentence with no filler. Its brevity is appropriate structurally, though the content is too thin for the tool's complexity.

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 four parameters, 0% schema coverage, no output schema, and only a readOnlyHint annotation, this description is insufficient. An agent cannot reliably infer what 'target' does or how artifacts, tags, and scan overviews are returned.

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% across four parameters, so the description must compensate but does not. It mentions 'repository' only, leaving 'project', 'limit', and especially 'target' (likely a tag or digest selector) entirely undefined for the agent.

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 does identify a list operation over artifacts in a repository, but it bundles 'tags and scan overviews' into the same sentence without clarifying whether they are returned as embedded fields or separate resources. Given siblings like harbor_artifact, harbor_tags, and harbor_vulnerabilities, the scope remains ambiguous to an agent choosing between them.

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 when-to-use guidance, no alternative tools named, and no indication of when this should be preferred over harbor_artifact, harbor_tags, or harbor_vulnerabilities. The only contextual hint is the '[READ]' marker, which does not distinguish it from other read tools.

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