helm_diagnostics

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

Since no annotations were provided, the description carries full burden. It discloses that the tool retrieves CPU, memory, and other system data without side effects. It does not mention destructive actions or authorization needs, but the read-only nature is evident from the 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?

A single sentence front-loads the core verb and resource, then lists specifics efficiently. No redundant words.

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?

Without an output schema, the description adequately describes the return value categories. It is complete for a diagnostic tool, though a brief mention of data format could enhance completeness.

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 (100% schema coverage trivially). The description adds value by enumerating the categories of diagnostics returned, which goes beyond the empty 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 specifies the verb 'Get' and the resource 'host diagnostics' with a detailed list of included metrics (CPU, memory, swap, disks, uptime, etc.). It distinguishes the tool from siblings like 'helm_health' and 'helm_system_info' by being more comprehensive.

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 for retrieving host diagnostics without explicitly stating when to use it versus alternatives or when not to use it. No tools are suggested for comparison, leaving the agent to infer context.

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