promote_user

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

No annotations are provided, so the description must disclose behavioral traits. It does mention the required service_key for authorization, but lacks details on reversibility, idempotency, or what happens if the user already has the role. The extra sentence about admin secrets is tangential.

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 three sentences, but the second sentence about admin secrets is only tangentially related and adds unnecessary length. The purpose is front-loaded, but the structure could be tighter without the digression.

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 no output schema and moderate complexity, the description covers the basic purpose and a required authorization. However, it omits important context such as required preconditions (user must exist in the project), potential errors, and output format. It is adequate but has clear gaps.

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%, so the baseline is 3. The description adds minimal value beyond the schema: it implies the 'email' parameter is the user's email address and that 'project_id' is a project identifier. No additional constraints or formats are given.

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 action 'Promote a user to project_admin role' with the specific verb 'promote' and resource 'user to project_admin role'. It distinguishes from the sibling tool 'demote_user' which performs the opposite action.

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 mentions a prerequisite 'Requires service_key' but lacks explicit guidance on when to use this tool versus alternatives like 'demote_user' or 'set_org_member_role'. The usage context is implied but not clearly delineated.

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