list_manifestworks

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which covers safety. The description adds that the listing is scoped to a cluster and represents hub management, but does not disclose open-world behavior (openWorldHint=true) or return format/pagination. Minimal added context beyond annotations.

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 extremely concise: one sentence plus a compact Args block. No filler or redundancy; every word contributes to understanding the tool's purpose and parameter.

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?

Given the simplicity (one param), presence of an output schema, and clear annotations, the description is sufficient for selection and invocation. It could mention when to use this instead of get_manifestwork or list_manifestworkreplicasets, but this is not critical for a basic list tool.

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?

The input schema has 0% description coverage, but the description's 'Args' section clarifies that 'cluster' is the managed cluster name, which is the essential semantic. This compensates for the bare schema, though it is sparse for a single parameter.

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 clearly states the action 'List', the resource 'ManifestWorks', and a specific scope 'targeting a cluster' with added context 'what the hub is managing there'. This distinguishes it from sibling tools like get_manifestwork (singular) and list_manifestworkreplicasets.

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 clear usage context: use this to see what the hub is managing on a specific cluster. It does not explicitly enumerate alternatives or exclusions relative to siblings like get_manifestwork, but the listing verb and per-cluster scope provide sufficient guidance for selection.

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