cluster_utilization

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

The description includes '[READ]' indicating a read-only operation and 'Point-in-time' clarifying the nature of the data. Since no annotations are provided, this is good coverage for a simple retrieval tool.

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 concise, front-loaded with the purpose, and lists parameters efficiently. Every sentence adds value without fluff.

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?

The description adequately covers the tool's purpose and parameters for a simple read operation. It lists the metrics (CPU, memory, storage, IOPS), though it lacks output structure details, which is acceptable given no output schema.

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 description explains that cluster_ext_id is from cluster_list and that target can be omitted for the default config. This adds meaning beyond the schema, which has 0% description coverage.

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 it retrieves point-in-time CPU, memory, storage, and IOPS utilization for a cluster. The verb 'READ' and specific resource make it distinct from sibling tools like cluster_health.

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 mentions that cluster_ext_id comes from cluster_list, providing some context. However, it does not compare this tool to alternatives like cluster_health or explain when to use it over others.

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