Check IaC Job Status

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

With no annotations, description indicates it checks status and retrieves results, and mentions potential delay. Does not disclose polling behavior, idempotency, or error handling, but covers essential behavior.

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 sentences, front-loaded with purpose, efficient and no wasted words.

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 monitoring tool with one parameter, description covers purpose, usage sequence, and timing. Lacks output format but acceptable given no output schema and low complexity.

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% for 'jobId'. Description adds context by specifying 'Job ID returned from generate IaC request', linking to sibling tool and clarifying origin beyond 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?

Description clearly states the verb 'check' and resource 'status and results of an Infrastructure as Code generation job'. It differentiates from sibling 'generate-iac' by indicating this tool is used to monitor a previously initiated job.

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?

Explicitly states to use after calling 'generate-iac' to monitor progress and get results, including a time estimate of up to 1 minute. Lacks exclusions or alternatives but provides clear context.

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