Get project IAM policy

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

With no annotations, the description carries the full burden, and 'Fetches' does signal a non-mutating read. However, it discloses nothing about required permissions (e.g. resourcemanager.projects.getIamPolicy), consistency behavior, or what the returned policy contains beyond 'role bindings'. Adequate for a low-risk read but thin on behavioral context.

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?

One sentence, front-loaded with the verb and the resource, with zero filler. Nothing is wasted and the essential information arrives immediately.

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?

For a simple one-parameter read tool this covers the basics, but with no output schema the description should at least sketch the returned policy shape (bindings list, etag, version) since that is the main thing an agent needs to reason about. It stops at 'role bindings', leaving the return contract underspecified.

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 single projectId parameter is already documented in the schema, including the GOOGLE_CLOUD_PROJECT default. The description adds no syntax, format, or fallback detail beyond what the schema provides, so the baseline 3 applies.

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 ('Fetches') and resource ('the full IAM policy (role bindings) for a project'), clarifying what is returned beyond the bare tool name. It is implicitly distinguishable from the write siblings (gcp_set_project_iam_policy, gcp_add_project_iam_binding, gcp_remove_project_iam_binding) via the get/fetch verb, but it never explicitly contrasts itself with them.

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 when-to-use guidance and no alternatives are named, despite four closely related IAM siblings where the read-vs-write distinction matters. The agent must infer that this is the inspection counterpart to the set/add/remove tools.

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