harbor_replication_task_log

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

The readOnlyHint annotation already covers the safety profile, and the description adds real value beyond it by disclosing that the return is plain text and 'bounded' (i.e. possibly truncated), which an agent needs to know. It stops short of saying how the bound works, whether truncation is flagged in the output, or what happens on an unknown task id.

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, correctly leading with the mode tag, then verb, then resource. It is efficient, though its brevity is arguably under-specification rather than tight editing.

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?

Placeholder.

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 all three parameters, so the description carries the full burden and does not meet it: execution_id, task_id, and target are never explained. The description only obliquely implies a task must be identified; nothing clarifies what 'target' selects or how execution_id relates to task_id.

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 states a specific verb+resource ('Read the ... log of a replication task') and flags the mode with a '[READ]' prefix, so an agent can distinguish it from write-side siblings like harbor_replication_policy. It does not name the near-identical log siblings (harbor_retention_task_log, harbor_gc_log, harbor_scan_log), so differentiation is implied by the noun rather than stated.

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 guidance on when to use this versus harbor_replication_execution, harbor_replication_tasks, or the other *_log tools, and no prerequisite is given even though execution_id and task_id must be obtained elsewhere. The only usage signal is the weak '[READ]' tag and the word 'bounded', which implies truncation but not selection criteria.

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