hostodo_get_vm_metrics

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

The description fully discloses behavioral traits: it is a stub, does not execute the requested action, returns a 'coming_soon' response, and records demand. It also warns against sending secrets. With no annotations provided, the description carries the full burden and excels in 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 extremely concise, using two sentences to convey purpose, current behavior, and a warning. Every sentence is essential, and the most critical information is front-loaded.

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 the tool has no output schema and no annotations, the description adequately covers the tool's current state, its non-functional nature, and security considerations. It is comprehensive for a stub tool with 4 optional parameters.

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% with parameter descriptions already present, so baseline is 3. The description adds no further meaning to parameters beyond the schema, though it includes a general security warning ('Do not send secrets').

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's purpose: 'Get VM resource metrics.' It further clarifies that it is currently a stub that records demand and does not perform the action, distinguishing it from functional sibling tools like hostodo_get_bandwidth_usage and hostodo_check_vm_health.

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 implies usage for recording demand rather than actual metrics retrieval, but it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions. The 'Coming soon' label hints at future functionality but lacks concrete guidance.

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