get_vm_stats

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing beyond a raw endpoint reference. It does not disclose what statistics are returned, their freshness, or any rate-limit/polling behavior — the parenthetical is a restatement of the API route, not behavioral context.

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?

It is a single short fragment with no waste, but it is undersized rather than efficiently front-loaded — the endpoint parenthetical occupies space that could have carried meaningful scope information.

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 one-parameter read-only tool with annotations covering the safety profile and full schema coverage, the minimum is met. What is missing is any indication of the returned statistics (no output schema exists), which matters most for a 'stats' tool.

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 100% with a single required 'id' parameter already documented as 'Virtual machine ID'. The description adds no format, range, or acquisition guidance beyond the schema, so the baseline 3 applies.

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 names a specific resource (virtual machine statistics) and implies retrieval, and the endpoint path (vm/load_stats) narrows it further. However, it never states the verb explicitly nor what 'statistics' means, so an agent cannot tell it apart from siblings like get_vm_engine or get_snapshots without guessing.

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?

There is no guidance on when to call this tool, what prerequisites exist, or which sibling to prefer for related VM data (get_vm_engine, get_power_status, get_server_sensors). The agent is left to infer usage entirely from the name.

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