gcp_add_project_iam_binding

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

No annotations are provided, so the description carries full burden. It only states 'Grant an IAM role,' implying addition, but fails to disclose whether the action is idempotent, if it appends to existing bindings, or what the response looks like. The behavioral impact is underspecified.

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?

The description is extremely concise with two sentences. The first sentence states the purpose, and the second provides necessary format examples. No unnecessary 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?

Given the lack of annotations and output schema, the description is incomplete for a mutation tool. It does not explain the result (e.g., returns nothing or updated policy), whether the operation is synchronous, or how to handle errors. Critical context for safe invocation is missing.

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% with basic descriptions. The description adds value by providing concrete format examples for member ('user:email', 'serviceAccount:email', etc.) and role ('roles/editor', etc.), which aids correct invocation. This extra context justifies a score above the baseline of 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?

The description clearly states the tool's purpose: 'Grant an IAM role to a member on a GCP project.' This is a specific verb-resource combination that distinguishes it from sibling tools like gcp_remove_project_iam_binding and gcp_get_project_iam_policy.

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 description provides format hints for member and role parameters, but does not explicitly state when to use this tool versus alternatives. It lacks guidance on prerequisites, such as required permissions or that this tool adds a binding rather than replacing the entire policy.

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