linear_updateTeamMembership

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

No annotations exist, so description must compensate. It mentions 'role' but the schema only includes 'owner' (boolean) and 'sortOrder' (number), not a 'role' field. No disclosure of permissions, side effects, or failure conditions.

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?

Single sentence plus instruction is concise and front-loaded. No wasted words, but could be slightly more structured to list the fields.

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?

No output schema and minimal description. Lacks explanation of field meanings, return values, error cases, and source of membership IDs. Incomplete for an agent to use confidently.

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 33% (only id described). Description adds 'at least one other field' but does not explain what 'owner' or 'sortOrder' mean, leaving agents to infer their semantics.

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 'Update a user's role in a team' with a specific verb and resource, distinguishing it from sibling tools like linear_addUserToTeam and linear_removeUserFromTeam.

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?

Explicitly requires 'id plus at least one other field to change', providing a clear usage instruction. Lacks explicit when-not-to-use or alternatives, but the context of siblings implies the tool is for updates only.

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