get_capacity_overview

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

Beyond annotations, discloses that values are None while analytics warm up and that percentage metric exists only at group level, adding critical 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 with a clear lead summary, detailed bullet points, and parameter documentation. Slightly verbose in listing all metrics but no redundancy.

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 no output schema, the description sufficiently describes return values (percentage, absolute amounts, projected days) and warming behavior. All necessary context for an agent to invoke and interpret results is present.

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?

With 0% schema coverage, the description fully explains each parameter: cluster_id as a UUID from list_resources and target as an optional config value, providing essential meaning absent 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 clearly states the tool gets a capacity overview for a cluster, listing specific metrics (remaining-capacity percentage, per-dimension absolute remaining, projected days-until-full). It differentiates from siblings by directing users to alternative tools for specific needs.

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 recommends starting here for overall health and directs to 'get_remaining_capacity' for headroom or 'get_time_remaining' for projections, providing clear when-to-use and when-not-to-use guidance.

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