pve_metrics_server_set

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

Without annotations, the description carries full burden. It discloses that this is a mutation (write operation), that it runs in dry-run mode by default requiring explicit confirmation, and that it only affects configuration. This covers key behavioral traits but lacks details on permissions or side effects.

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 extremely concise—only two sentences—and front-loaded with 'MUTATION: create-or-update', immediately conveying the action. Every sentence is meaningful and efficiently communicates the key points.

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 tool has 8 parameters, one required, and an output schema, the description is minimal. It covers the action and dry-run behavior but does not explain prerequisites, return values (though output schema exists), or edge cases like handling duplicate metrics_id. It is adequate but incomplete.

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 no parameter-level information beyond the input schema. With schema description coverage at only 13%, the description should compensate but does not mention any parameters like metrics_id or port. The low coverage and lack of parameter explanation result in a low score.

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 tool creates or updates a PVE metrics server definition. The verb 'create-or-update' and resource 'PVE metrics server definition' are specific. Among siblings like pve_metrics_server_delete and pve_metrics_server_list, this tool's purpose is distinct.

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 provides clear usage guidance: dry-run by default, confirm=True to execute. It also notes that it is config-only and metrics forwarding adjusts to new settings, implying it is for configuration changes. However, it does not explicitly exclude other scenarios or compare to sibling tools.

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