pve_diagnose

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

Without annotations, the description carries the full burden. It states READ-ONLY and lists gathered evidence, but lacks details on authentication requirements, rate limits, or the behavior when the node parameter is omitted. Minimal but not misleading.

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, front-loaded sentence with no filler. Every word adds value, clearly stating the tool's read-only nature and the specific evidence gathered.

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?

Given the presence of an output schema, the description does not need to detail return values. However, it lacks context on when to use the tool over siblings (e.g., pve_doctor) and does not clarify the scope (single node vs. cluster). Adequate but not comprehensive.

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 description coverage is 50% (only proximo_target described). The description adds no parameter-specific information beyond the schema; it does not explain the 'node' parameter's meaning or how the tool uses it.

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 uses a specific verb 'gather' and resource 'node health evidence', listing concrete items (status, storage usage, recent failed tasks, flags). It clearly conveys the tool's purpose and distinguishes it from siblings like pve_doctor and pve_node_status.

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 explicit guidance on when to use this tool versus alternatives such as pve_doctor, pve_node_status, or other diagnostic tools. The READ-ONLY label implies safety but does not provide contextual usage hints.

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