GrantMemberProjectRoles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a grant operation (implying mutation/permission assignment) but doesn't disclose important behavioral traits like required permissions, whether this overwrites existing roles, what happens if the user doesn't exist, rate limits, or what the response looks like. For a permission-granting tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence in Chinese that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 role-granting mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after granting roles (success/failure responses), what valid RoleCodes are, permission requirements, or error conditions. The context demands more behavioral and operational information than provided.

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%, so the schema already documents all three parameters (ProjectId, UserId, RoleCodes) with their descriptions. The description doesn't add any parameter-specific information beyond what's in the schema, such as format examples for RoleCodes or where to find UserId values. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('授予' meaning 'grant') and resource ('工作空间成员新的空间角色' meaning 'workspace member new workspace roles'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its sibling 'RevokeMemberProjectRoles', which handles 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing admin permissions), when not to use it, or how it differs from similar tools like 'CreateProjectMember' or 'UpdateProjectMember' in the sibling list.

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