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

The readOnlyHint annotation already covers the safety profile, and 'Read-only' merely restates it. The description does add genuine behavioral context beyond the annotation: it discloses the record contents (run time, status, indexed items), which is valuable given there is no output schema. It omits pagination behavior for page/page_size.

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?

Two tight sentences, front-loaded with what the tool returns and followed by the when-to-use condition. The parenthetical CLI twin reference is compact and helps an agent map the tool to known behavior; no sentence is filler.

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, the description correctly compensates by describing the returned job fields, and the read-only nature is declared. It is nearly complete for a filtered-list tool; only pagination/ordering behavior is left unstated.

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 100%, so registry_name, status, page, and page_size are all already documented in the schema. The description adds no format, default, or filtering detail beyond that, so the baseline 3 applies.

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 ('the sync jobs of one Helm registry') and enumerates what each job record contains (run time, status, what it indexed). It is clearly distinguishable from neighbors like list_helm_registries (registries themselves) and sync_helm_registry (the action that triggers a sync).

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?

Gives an explicit diagnostic trigger: use it 'when a chart or version is missing from list_available_charts to see whether the registry synced.' This names the sibling alternative and the exact condition that selects this tool over it.

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