deploy_web_server

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

The description lists the resources created and the return values (public_ip, URL) but lacks details on failure behavior, permissions, idempotency, or cleanup. With no annotations provided, the description carries the burden and is moderately transparent.

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?

Single sentence of 13 words, front-loaded with the key concept 'One-shot'. Every word adds value with no 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?

Despite the clear purpose, the description omits parameter guidance and return format beyond public_ip and URL. With 10 parameters, no output schema, and no annotations, the description is too brief to fully instruct an agent.

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 description coverage is 0%, and the description does not explain any of the 10 parameters (e.g., compartment_id, shape, ssh_public_key). The agent must infer meaning from parameter names only, which is insufficient.

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 states it deploys a web server with all networking components (VCN, IGW, route, seclist, subnet) and an NGINX instance in one operation, and specifies the output (public_ip, URL). This distinguishes it from sibling tools that create individual resources.

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 'One-shot' phrasing implies this is for rapid, comprehensive deployment rather than step-by-step resource creation. While it doesn't explicitly state when not to use it or name alternatives, the context of sibling tools (e.g., create_vcn, launch_instance) makes the use case clear.

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