eng.manage_infrastructure

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

No annotations are present, so the description must disclose behavioral traits. It mentions 'modify' but fails to disclose that the 'delete' action permanently destroys resources. It also inaccurately emphasizes read-only 'view' operations without warning about side effects, leaving the agent unprepared for destructive consequences.

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?

A single, front-loaded sentence that efficiently conveys the tool's scope. It avoids redundancy and is easy to parse, though it could briefly mention side effects without bloating.

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 tool with a destructive delete action and no annotations, the description is underspecified. It omits any warning about irreversible changes, return formats, or required permissions. The sibling tools are clearly different, but the description doesn't cover the high-risk nature of the delete operation.

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 basic property descriptions. The description adds context by naming specific resource types (EC2, RDS, S3) that align with the resource_type enum, and mentions outputs like status/IP addresses. However, it doesn't explain what each action (list, status, delete) does or how resource_id relates to them, offering only marginal added value.

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 identifies the resource domain (cloud infrastructure: EC2, RDS, S3) and the general actions (query or modify). It distinguishes from sibling tools focused on repos, deployment, or CI by emphasizing infrastructure management, though it doesn't enumerate the specific actions (list/status/delete) which are left to the schema.

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 implies usage for cloud infrastructure management but provides no explicit guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites. It doesn't mention that it's the go-to for EC2/RDS/S3, which limits selection confidence.

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