list_clusters

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds useful context beyond annotations: clusters may come from config and Kubernetes discovery, credentials are never returned, and discovery_error explains failed discovery.

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 compact and front-loads the resource being returned. Both sentences earn their place by covering sources, excluded sensitive data, and the discovery_error field.

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 simple no-parameter interface, rich annotations, and existing output schema, the description is largely complete. It explains the sources and a notable error field, though it could do more to position the tool against related cluster-inspection siblings.

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?

This tool has zero parameters, so parameter semantics are inherently minimal. The baseline for a 0-parameter tool is 4, and there are no misleading parameter claims in 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 clearly identifies the resource as Flink clusters and explains that they come from the config file and optional Kubernetes discovery. It is more specific than a tautology, but it does not explicitly differentiate this tool from nearby siblings such as cluster_overview, cluster_config, or list_flink_deployments.

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 describes sources and output content but gives no explicit guidance on when to use this tool versus alternatives like cluster_overview or list_flink_deployments. Usage is only indirectly implied by the tool name and purpose.

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