container_status

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

No annotations provided, and description offers no behavioral traits beyond 'get'. Does not confirm idempotency, permissions, rate limits, or any side effects. For a read operation, this is a significant omission.

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?

Single sentence is concise but too brief for a meaningful tool description. It sacrifices informational value for brevity.

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?

Without output schema, annotations, or parameter explanations, the description fails to equip an agent with sufficient information to understand return values, errors, or usage constraints.

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 0%. Description does not explain the semantics of node or vmid parameters, nor does it provide any additional context beyond schema types.

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?

Description clearly states the verb 'Get' and resource 'runtime status of an LXC container', distinguishing from VM-related tools like vm_status and from container config tools. However, does not specify that it returns a single status object, leaving slight ambiguity.

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?

No guidance on when to use this tool versus alternatives such as container_config or list_containers. No context about prerequisites or scenarios where status is needed.

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