VPS_getMetricsV1

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

No annotations provided; description implies a read operation but lacks details on data freshness, aggregation, rate limits, or other behavioral traits beyond the basic purpose.

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?

Description is concise, with a clear main action, bulleted metrics list, and usage sentence. No unnecessary words, though the bullet list could be inline.

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?

Covers metric types and general purpose, but lacks details like time interval, data retention, or timezone handling. Adequate for a simple tool but incomplete for deeper understanding.

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?

Input schema covers 100% of parameters with descriptions, and the tool description does not add additional semantic meaning to parameters beyond what is already in the schema.

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 retrieves historical metrics for a VPS and lists specific metrics (CPU, memory, disk, network, uptime), making it distinct from siblings like VPS_getScanMetricsV1 or VPS_getBackupsV1.

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?

Describes the use case 'monitor VPS performance' but provides no explicit guidance on when to use versus alternatives (e.g., VPS_getScanMetricsV1) or when not to use.

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