list_tkc_clusters

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds that it returns 'total count and list of clusters with status and K8s version', and clarifies the filtering behavior, providing useful context beyond the 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: a title line with [READ], bullet-pointed args, and a returns line. No extraneous information, front-loaded with purpose, and efficiently structured.

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 tool's simplicity (listing with optional filters) and no output schema, the description covers the main aspects: parameters and return format. It could mention pagination or sorting, but for a typical list tool, it is sufficiently complete.

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 coverage is 0%, so the description fully compensates by explaining that namespace filters by vSphere Namespace (lists all if not specified) and target is the vCenter target name. This adds meaningful semantics missing from the schema.

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 explicitly states 'List TanzuKubernetesCluster (TKC) clusters', providing a specific verb and resource. It distinguishes itself from siblings like get_tkc_cluster (which retrieves a single cluster) and list_namespaces (which lists namespaces), making the purpose clear.

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 explains the parameters (namespace and target) and their default behavior, implying when to use them. However, it does not explicitly state when not to use this tool or recommend alternatives among siblings, leading to only implicit guidance.

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