reboot_container

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

Annotation indicates non-destructive (destructiveHint: false), and description aligns. However, no additional traits disclosed: e.g., whether reboot is graceful or forced, any side effects, or required permissions.

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?

Extremely concise single sentence. For a simple tool, this is acceptable, though a bit more structure (e.g., listing parameters) could help.

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 straightforward reboot action with complete schema coverage, the description is minimally adequate. However, given sibling tools like 'reboot_vm', a note on applicability or differences would improve completeness.

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 covers both parameters with descriptions. Description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 is a single clear verb+resource: 'Reboot a container'. It immediately communicates the action and distinguishes from siblings like 'reboot_vm', which reboots a VM.

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 like 'stop_container' followed by 'start_container' or 'shutdown_container'. No mention of prerequisites or context.

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