harbor_retention_task_log

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

The readOnlyHint annotation already establishes that this is a safe read operation, so the description does not need to repeat that. It adds that the log is 'bounded plain-text', which is useful behavioral context, but it does not explain what 'bounded' means in practice, whether output is truncated, or what happens when no log exists.

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 the [READ] tag, specific verb, and resource. There is no redundant or wasted wording.

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 four parameters, three of them required, no schema descriptions, and no output schema, the description should explain parameter relationships and clarify the return format. It says only that the tool reads a bounded plain-text log, which is not enough for an agent to confidently supply policy_id, execution_id, task_id, and optional target.

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%, and the description provides no meaning for policy_id, execution_id, task_id, or target. It only identifies the overall resource, leaving all four parameters undocumented in both the schema and the description.

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, 'Read', and resource, 'bounded plain-text log of a retention task', so an agent knows this retrieves log output rather than retention task metadata. It does not explicitly name sibling alternatives such as harbor_retention_tasks or harbor_replication_task_log, which keeps it 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 description implies that this tool is used to read a retention task log, but it gives no explicit when-to-use guidance, no prerequisites, and no comparison to adjacent tools like harbor_retention_tasks or other log tools. An agent must infer the selection criteria 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.