list_flux_kustomizations

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral detail that the tool returns ready/suspended/revision status, which implies a read-only operation. It does not mention authentication or error cases, but for a simple list tool this is acceptable.

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, concise sentence that front-loads the key action, resource, and scope. Every word earns its place with no redundancy.

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?

For a simple list tool with well-documented schema parameters and no output schema, the description adequately explains what it returns (status fields) and the namespace scope. It is fully sufficient for an agent to understand the tool's purpose and output.

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 high (100%) with both 'cluster' and 'namespace' explained. The description adds the context of listing in a namespace, but this does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('Lists'), clearly identifies the resource ('Flux Kustomizations'), states scope ('in a namespace'), and specifies the returned information ('ready/suspended/revision status'). It effectively distinguishes from sibling tools like list_flux_helm_releases and list_flux_sources.

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 provides clear context for when to use the tool—listing Kustomizations per namespace or all namespaces (via parameter hint). Although it does not explicitly state when not to use it or name alternatives, the context is sufficient given the tool's focused purpose.

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