Generate Infrastructure as Code

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

Discloses it initiates a long-running job and returns a job ID, which is key behavioral info. But with no annotations, it doesn't cover destructive nature, permissions, or failure modes.

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 clear sentences with no fluff. Could add more context (e.g., response format) without losing conciseness.

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?

Covers purpose and async behavior adequately but lacks return value details and error scenarios. With no output schema, description is minimally sufficient.

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 100% with clear descriptions for both parameters, including a cross-reference to get-cloud-resources. Description adds no extra parameter info, so baseline 3.

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?

Clearly states the specific action 'Generate Infrastructure as Code' and the resource type 'cloud resources'. Distinguishes from siblings like check-iac-job-status by noting it initiates a long-running job and returns a job ID for tracking.

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?

Mentions it returns a job ID for tracking, implying use with check-iac-job-status, and references get-cloud-resources for finding IDs. However, lacks explicit 'when not to use' or alternatives.

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