get_cluster_hardware_analytics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the tool connects over SSH and returns a Markdown table, which is useful. However, it does not mention potential side effects, authentication requirements, latency implications, or what happens if SSH fails. The description is honest but incomplete on behavioral traits.

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 sentence that front-loads the core purpose (real-time CPU load and memory allocation), specifies the scope (every configured cluster host), the method (over SSH), and the output format (Markdown table). Every element earns its place with zero waste.

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 zero-parameter tool with no output schema, the description covers the main purpose and output format. However, it lacks context about failure modes, authentication prerequisites, or how this relates to sibling tools like get_cluster_infrastructure_health. An agent might not know when to prefer this over the infrastructure health tool.

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 schema provides no parameter semantics to cover. The description compensates by explaining what data is fetched and how it is presented. With no parameters, the baseline is 4, and the description adds meaningful context about the tool's behavior.

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 fetches real-time CPU load and memory allocation for every configured cluster host over SSH, and specifies the output format as a Markdown table. This is a specific verb+resource combination that distinguishes it from siblings like get_cluster_infrastructure_health, which likely covers broader health metrics.

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 usage context (real-time hardware monitoring for cluster hosts) but does not explicitly state when to use this tool versus alternatives like get_cluster_infrastructure_health. There is no mention of when not to use it or what conditions would make a sibling tool more appropriate.

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