List Cluster Sizes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds non-obvious context beyond that: the auth requirement (user credential such as OAuth, enforced by the RawTree API) and the mandatory call-before-create-cluster sequencing driven by a 'current backend-controlled catalog' that can change.

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?

Four labeled sections, each front-loaded and each earning its place: purpose, return contents, auth, and the critical call-ordering rule. No filler or restatement of the name.

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?

With no output schema, the description compensates by enumerating what comes back (per-replica sizes, min/max replica counts, default vertical autoscaling bounds). Combined with the auth note and the mandatory pre-create-cluster ordering, an agent has everything needed to call this correctly.

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 takes zero parameters, so the baseline is 4. The description correctly adds no parameter guidance, and its 'Returns' section describes the output shape rather than inventing inputs.

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?

States a specific verb (List) and a precise resource (RawTree cluster creation options: per-replica sizes, replica counts, autoscaling bounds). This is clearly distinguishable from sibling list-clusters, which enumerates clusters rather than the catalog of valid sizes.

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?

Explicitly states when to use it and imposes a hard ordering constraint: 'You MUST call this tool before create-cluster so replicas and both sizes come from the current backend-controlled catalog.' The alternative/blocking relationship with a named sibling is spelled out, leaving nothing to inference.

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