iaas_create_deployment

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes only the POST path, which simply restates the annotation title, and adds no new behavioral context such as side effects or whether a request/task is created.

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?

It is short and front-loaded, but 'Create deployment' and 'Create a new Deployment' are redundant, and the raw endpoint line duplicates the annotation title without adding meaning.

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?

Annotations cover the mutation/safety profile, so the description needn't explain reversibility. However, for a nested-body creation tool with no output schema, the description says nothing about what a successful call yields (a request, a deployment id, a task) or how it relates to the deployment request flow.

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 100% and the nested body fields (name, projectId, description) are each documented, so the schema carries the load. The description adds nothing about the body or apiVersion parameter, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Create a new Deployment') plus the underlying POST endpoint, so an agent can tell it creates a deployment object. It stops short of differentiating from the near-identical 'onboarding_post_deployment' sibling, which is the main risk for selection.

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?

There is no guidance on when to use this versus onboarding_post_deployment, or versus iaas_get_deployments/iaas_get_single_deployment. No prerequisites (project membership, required body) are mentioned.

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