list_standard_clusters

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

No annotations are provided, so the description carries the transparency burden. 'List' implies a read-only operation, and the description specifies what data is returned (aliases and URLs) and the environment scope. However, it does not explicitly state that the operation is side-effect-free or require special permissions.

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, focused sentence with the verb and resource upfront, no unnecessary words, and clearly communicates the tool's core function.

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 no-parameter, read-only list tool with an output schema, the description adequately states the purpose and content. The only minor gap is the lack of explicit guidance on how this differs from 'list_clusters', but the simple nature of the tool makes this non-critical.

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 tool has zero parameters, so the baseline is 4. The description adds meaning by explaining that the output consists of built-in cluster aliases and API/OAuth URLs for each environment, which helps the agent understand the result without needing parameter details.

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 ('List') and resource ('standard clusters'), and clarifies the output includes aliases and API/OAuth URLs for dev/uat/prod environments. This distinguishes it from the sibling tool 'list_clusters', which likely lists registered clusters.

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 this is for retrieving built-in cluster information, but does not explicitly state when to use it versus 'list_clusters' or other cluster management tools. No alternatives or exclusions are mentioned.

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