aws_reboot_instance

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

Given no annotations, the description provides useful behavioral context: 'Brief OS-level restart; billing continues.' This informs the agent of the restart type and billing impact. However, it does not disclose potential side effects like process termination or data loss.

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 concise with three sentences, no redundancy, and front-loads the purpose. Every sentence adds value: purpose, behavior, usage requirement.

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 simple reboot tool with no output schema, the description adequately covers purpose, key behavioral traits, and a usage requirement. It lacks detail on return value or error handling, but is sufficiently complete given the tool's simplicity.

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 clear descriptions for both parameters (instance_id and region). The tool description adds no additional meaning beyond the schema, so a 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?

The description clearly states 'Reboot a running AWS EC2 instance', which specifies the verb (reboot) and resource (running EC2 instance). This distinguishes it from sibling tools like aws_start_instance, aws_stop_instance, and aws_terminate_instance.

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 includes 'Confirm with the user before calling' as a usage guideline, but lacks explicit guidance on when to use this tool versus alternatives. No mention of alternative tools or 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.