list_tkc_clusters

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), the description explains the return envelope structure, guarantees 'truncated is always False' due to walking the Supervisor list, and warns about a deprecated 'clusters' alias. This adds meaningful behavioral context.

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 well-structured and front-loaded with the action and resource. It includes return format, workflow guidance, deprecation note, and parameter explanations without redundancy or wasted words.

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 complexity and lack of output schema, the description adequately documents the return envelope, pagination behavior, and next-step suggestions. It covers all essential invocation context, making it complete for an AI agent.

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 0%, but the description compensates by explaining both parameters: namespace as a filter with 'omit to list every one' and target as the vCenter in config.yaml with a default. This adds substantive meaning beyond the raw 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 specifically states 'List TanzuKubernetesCluster (TKC) clusters, optionally in one namespace', using a clear verb and resource. It also distinguishes itself from related tools by mentioning get_tkc_cluster and get_tkc_kubeconfig for follow-up actions.

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?

Explicit guidance is provided: 'Start here, then call get_tkc_cluster for full detail or get_tkc_kubeconfig for access.' It also clarifies that omitting namespace lists all clusters, and provides deputy default behavior for target.

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