harbor_project_audit_logs

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

readOnlyHint=true already declares the safety profile, so the leading '[READ]' tag adds nothing. The description does contribute the scope caveat about MCP governance audit, but says nothing about ordering, pagination, or result volume for what is a log-listing endpoint.

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 no filler; the read tag and the disambiguation clause are both immediately visible. Brevity here edges toward under-specification rather than verbosity, so it is efficient but thin.

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, 0% schema description coverage, and an undocumented 'target' parameter, the definition leaves too much unresolved for a log-retrieval tool. An agent cannot tell what 'target' filters or how 'limit' interacts with paging.

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 must carry the burden for three parameters. It only implies 'project' via 'a project's audit logs' and gives no meaning at all for 'limit' (default 50) or 'target', leaving two of three parameters opaque.

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 and resource ('List a project's Harbor audit logs') and adds a scope boundary excluding the MCP governance audit. That boundary distinguishes it from a related concept rather than from a named sibling tool, so it stops short of a 5.

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 'not the MCP governance audit' clause is an explicit when-not, which is real guidance. However, no sibling in the list (e.g., harbor_project, harbor_scan_log, harbor_gc_log) is named as the alternative for related log lookups, so routing is only partially resolved.

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