pve_metrics_server_list

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

States 'READ-ONLY' and 'No state change,' which is sufficient for a list tool. No annotations exist, so description carries full burden. Could mention expected output format (list of dicts) but does so. Lacks details on potential error cases or permissions needed.

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?

Three concise sentences with front-loaded key information. Every sentence adds value, no fluff.

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 that no annotations are present, the description covers the essential read-only nature, return content, and related mutation tools. Could mention that it retrieves configurations from PVE, but overall adequate.

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 100% for the single parameter; the description does not add extra insight beyond the schema's own description. Baseline 3 is appropriate.

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 starts with 'READ-ONLY: list all PVE metrics server definitions,' clearly stating the verb and resource. It distinguishes from sibling tools by naming pve_metrics_server_set and pve_metrics_server_delete for mutations.

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?

Provides explicit alternatives for create/update/delete, indicating when to use this read-only tool vs mutation tools. Does not elaborate on specific scenarios or prerequisites, but the guidance is clear and effective.

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