Get cached Proxmox node stats for a host

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds genuinely useful behavior: it returns an empty skeleton when no data has been collected yet, and it emphasizes that the returned value is the cached snapshot rather than a live fetch. This is meaningful beyond the structured annotations.

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?

Two short sentences with no filler. The main action and scope are front-loaded, and the fallback behavior is stated efficiently.

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 read-only, single-parameter getter, the description covers the essential invocation context and the degenerate no-data case. The main gap is that no output schema exists and the description does not indicate what fields or shape the Proxmox stats snapshot contains, so an agent lacks full visibility into the return value.

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?

Schema coverage is 0%, so the description carries the burden of explaining the required 'id' parameter. 'For a host' offers minimal meaning, implying id is a host identifier, but it does not explicitly state that id refers to a Termix host ID or explain where the value comes from. It is sufficient for a simple single-parameter tool, but not richly explanatory.

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 states a specific verb ('Get') and resource ('cached Proxmox node stats for a host') and clarifies that it returns the most recently polled snapshot, distinguishing it from the historical variant. The empty-skeleton fallback further pins down expected behavior.

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 phrase 'most recently polled' and 'cached' imply this is for current cached data rather than triggering new collection or fetching history. However, it never names sibling tools like get_historical_proxmox_node_stats_host or start_proxmox_stats_collection, nor states explicit when-not-to-use conditions.

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