harbor_replication_execution

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

The "[READ]" tag merely restates the readOnlyHint=true annotation already supplied, so it adds no new structured context. Nothing is said about what "state" comprises, what happens with an unknown execution_id, or permission requirements, which would be the valuable additions given annotations already cover safety.

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 short sentence with the read tag front-loaded; nothing is wasted. It is terse rather than padded, with under-specification being penalized in other dimensions.

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 and no parameter documentation, the description should have indicated what a replication execution's state includes (e.g. status, trigger, start time) and clarified the target parameter. For a lookup tool this leaves the agent guessing at the response shape.

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 mentions no parameters at all. The non-obvious "target" parameter is left completely unexplained, and even execution_id's required/singular semantics come only from the schema, not the prose.

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 ("Get the current state of one replication execution"), and the singular "one" implicitly separates it from the sibling list tool harbor_replication_executions. It is clear about what is fetched, though it does not name the sibling it contrasts with.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as harbor_replication_executions for listing or harbor_replication_task_log for per-task detail. Usage is only inferable from the word "one".

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