iaas_update_project

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, and the description only echoes the endpoint from the annotation title. It omits meaningful behavior for a PATCH-style update: whether omitted fields are preserved or cleared, whether member/viewer arrays are additive or replacing, and whether project configuration requires administrator privileges.

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 short lines with no wasted prose, and the action is front-loaded. But the endpoint line largely duplicates the annotation title ("PATCH /iaas/api/projects/{id}"), so part of the already-tiny description earns nothing new.

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 15+ field body, no output schema, and several sibling update tools that could be confused with it. For that complexity level, the description should explain patch semantics, required permissions, and how it differs from the other project update endpoints — none of which is present.

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 every body field (members, constraints, placementPolicy, zoneAssignmentConfigurations, etc.) is documented inline, so the schema carries the full burden. The description adds no extra semantics beyond the schema, which meets the 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?

States a verb and resource ("Update project") plus the underlying PATCH endpoint, so the basic action is clear. However, it does nothing to distinguish this from close siblings such as iaas_update_project_resource_metadata, iaas_update_project_zone_assignments, project_modify_project, or project_modify_project_principals — an agent cannot tell which project-update surface this covers.

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 versus the other project-mutation siblings, no prerequisites (e.g. admin role needed to change administrators), and no exclusions. The description is purely a restatement of the operation.

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