harbor_replication_executions

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

The [READ] prefix merely restates readOnlyHint=true, adding nothing beyond the annotation. The description says nothing about pagination behavior, default page size, ordering, or what happens when no filters are supplied for a read-only listing tool.

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 only redundancy is the [READ] tag, which duplicates the readOnlyHint annotation.

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 simple list tool this is under-specified: valid status values, the meaning of 'target', and the response shape are all absent, with no output schema or parameter descriptions to fall back on.

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, yet it only clarifies the status filter (calling it "upstream status"). The 'target' and 'limit' parameters are entirely undefined, and 'target' is genuinely ambiguous without explanation.

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 gives a specific verb and resource ("List replication executions") plus an explicit optional filter, which is enough to distinguish it from the singular harbor_replication_execution sibling. It stops short of naming the sibling tools it is not, so it lands at 4 rather than 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?

"Optionally filtered by upstream status" implies the main usage pattern, but there is no explicit when-to-use guidance, no pointer to harbor_replication_execution for single-record lookups, and no note about how this relates to harbor_replication_tasks or harbor_replication_task_log. Usage must be inferred from the name and sibling list.

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