Docker Container Resource Usage

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds two key behavioral traits: the snapshot nature (non-streaming) and the default/alternative target. No contradiction with annotations.

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 sentences, front-loaded with purpose, each sentence adds essential information. No redundancy or extra words.

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 simple tool (2 params, no output schema), the description covers what it does, its snapshot nature, and how to target instances. It could benefit from briefly noting the expected output format (e.g., JSON object with container stats), but completeness is adequate for the tool's complexity.

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% for both parameters (reveal, instance). The description adds context beyond the schema by explaining the default target, the dev alternative, and the importance of matching Coolify instance to avoid routing errors.

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 uses a specific verb 'Get' and resource 'current CPU, memory, network, and disk I/O usage for all running containers on the selected VPS.' It clearly distinguishes from sibling tools like vps_docker_ps (processes) and vps_docker_logs (logs) by focusing on resource stats.

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 states it's a 'one-shot snapshot (not streaming)' and specifies default target (Hetzner prod) with an alternative (dev via instance parameter). It warns about mismatched routing for Coolify containers. However, it doesn't explicitly contrast with other tools or state when not to use it.

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