iaas_create_project

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 write/non-idempotent profile is covered structurally. The description adds essentially nothing beyond the endpoint path: it says nothing about side effects, that the operation creates a new project entity with members/viewers/administrators, or about the validatePrincipals principal limit.

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 terse lines, front-loaded with the operation, with no filler. However, the second line merely repeats the annotation title ('POST /iaas/api/projects'), so it is redundant rather than value-adding, keeping it short of a 5.

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?

This is a complex mutation with a deeply nested body (member lists with principal types, constraint maps, zone assignment quotas) and no output schema. The rich schema offsets some burden, but the description says nothing about what gets created, return shape, or the principal-validation behavior, leaving a real gap for a complex write.

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%, with each nested field (name, members, constraints, placementPolicy, zoneAssignmentConfigurations, validatePrincipals) documented in the schema itself. The description adds no parameter meaning, so the baseline 3 applies when the schema does all the work.

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 states 'Create project', which is a verb plus resource, but it largely restates the tool name (iaas_create_project) and adds only the raw HTTP endpoint. It gives no hint of how it differs from other project-creating siblings such as project_post_projects or iaas_create_deployment, so an agent cannot distinguish them from the description alone.

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 tool, when not to, or what alternatives exist. It also omits prerequisites such as required permissions or whether the project must be created before zone assignments, so an agent gets no routing or precondition help.

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