run_command

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

Discloses automatic failover from SSH to SSM, a behavioral trait. However, no annotations exist, and description omits potential side effects (e.g., commands can be destructive, require permissions, or persist state).

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?

Two concise sentences front-loading the core purpose. Every word adds value without redundancy.

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?

Lacks output schema and does not describe return values, error handling, or execution status. Given tool complexity, output expectations should be mentioned.

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 clear descriptions. The description adds context on transport behavior, but instance_id and command semantics are already well-defined in the schema.

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?

Clear verb-resource pairing: 'Run a command on any managed instance.' Specifics about transport and failover distinguish it from sibling tools like check_status or aws_run_instances.

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?

Provides context on transport types and failover behavior but lacks explicit guidance on when to use this tool versus alternatives (e.g., aws_run_instances for creating instances, not running commands).

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