get-node

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description does not add behavioral traits beyond these, such as what the 'metrics' include or how missing nodes are handled. It is neither contradictory nor additive.

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 conveying the core purpose without extra words. Concise but missing detail about parameters and usage.

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 tool has low complexity (1 parameter, no output schema), and annotations cover read-only and open world. However, the description leaves out what metrics are returned and does not explain the parameter, which may confuse an AI agent without additional context.

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 only parameter 'name' has no description in the schema (0% coverage) and the tool description does not explain its purpose, format, or examples. The agent must guess what 'name' refers to (node name? hostname?).

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?

Clearly states 'Get metrics of an individual cluster node', which is a specific verb ('Get') and resource ('metrics of an individual cluster node'). It distinguishes from siblings like 'list-nodes' (list all) and 'get-node-memory' (specific metric).

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?

No guidance on when to use this tool versus alternatives. With many sibling tools for nodes (list-nodes, get-node-memory), the description should provide context for when to choose this one.

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