get_ec2_instances

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

With no annotations, the description carries the behavioral burden. 'Get' and 'see' clearly signal a read-only operation, and 'current state' indicates what the agent will receive. It does not discuss authorization, rate limits, or pagination, but for a straightforward list tool the lack of mutation is reasonably clear.

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 two tight, front-loaded sentences. The first gives the action and scope; the second gives a direct usage hint. There is no filler, repetition, or unnecessary qualifier.

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?

The description gives the output fields, the scope ('all'), and a concrete usage scenario, while the only optional parameter is fully handled by the input schema. It could better route the agent to siblings for single-instance or health-specific needs, but the gap is minor given the simplicity of this tool.

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?

The schema fully covers the only parameter with an enum and a documented default ('all'), so schema coverage is 100%. The description adds no parameter-level detail, but the baseline 3 is appropriate because the schema already does the heavy lifting.

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 identifies a specific verb 'get', a clear resource ('MoleCare EC2 instances'), and expected outputs (current state, IP addresses, instance types). The plural 'all' distinguishes it from the singular sibling get_ec2_instance, though it does not name that sibling explicitly.

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?

It gives a clear use case ('Use this to see all running servers') and the plural scope suggests it is for a broad list rather than a single instance. However, it does not explicitly say when not to use it or mention alternatives such as get_ec2_instance or get_ec2_health.

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