harbor_replication_tasks

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

readOnlyHint=true already declares this is a safe read, and the "[READ]" tag merely restates that. Beyond the annotation, the description adds only the scoping fact that results belong to a single execution; it says nothing about pagination despite a limit parameter, what a task record contains, or behavior when the execution has no tasks.

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?

One short, front-loaded sentence with no filler, which is good structure. However, the brevity crosses into under-specification — the sentence is too small for the parameter surface it must cover rather than efficiently dense.

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 read-only list tool with no output schema and a minimal annotation set, the description reasonably conveys what it returns (tasks belonging to one execution). The gap is the unexplained limit/target parameters, which a fuller definition should have addressed.

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 burden, but it only hints that execution_id identifies the execution. The limit parameter (default 50) and the target parameter — likely a registry endpoint filter — are entirely unexplained in both schema and description, leaving two of three parameters semantically 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 tasks") scoped to "one replication execution," which distinguishes it from harbor_replication_executions (executions, not tasks) and harbor_replication_task_log (singular log). The scope is clear enough to select it over siblings, though it does not name them explicitly.

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 description implies usage (inspect the tasks of a replication run) but gives no explicit when-to-use guidance, no prerequisites, and no mention of the clearly related sibling harbor_replication_task_log or harbor_replication_executions. The agent must infer the routing decision from the tool name alone.

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