pdm_pve_cluster_status

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

With no annotations, the description carries full burden. It indicates the tool is diagnostic (non-destructive) and 'live-proven', but lacks details on permissions, side effects, or rate limits. The existence of an output schema mitigates partial transparency.

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 concise and front-loaded with the purpose. Uses shorthand but remains clear. Minor improvement could include more structured formatting.

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 simple diagnostic tool with two parameters and an output schema, the description covers purpose, parameter hint, and prerequisite. It is sufficient for an agent to understand when and how to use it.

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 description adds meaning to the 'remote' parameter (source from pdm_remotes_list), compensating for its missing schema description. The 'proximo_target' parameter already has a detailed schema description. Overall, useful parameter guidance.

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 action ('get cluster status') and the resource ('PDM-registered PVE remote'), distinguishing it from the sibling 'pve_cluster_status' tool. The 'DIAGNOSE (LOW)' prefix clarifies its read-only nature.

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 notes that 'remote' must be from 'pdm_remotes_list' and requires 'PROXIMO_PDM_* config', providing usage context. However, it does not explicitly contrast with alternatives like 'pve_cluster_status'.

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