manage_team_member

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

No annotations are provided, so the description carries full burden. It describes the four actions and parameter behavior but does not disclose side effects, permission requirements, or results of actions. The mention of 'Enterprise feature' hints at privileged access but is insufficient for full transparency.

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 concise and front-loaded with the core action, followed by tier info and param details. It is well-structured but could be more compact; the blank line between sections is acceptable.

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 3-parameter tool with no annotations and no output schema, the description covers actions and tier constraints but omits return values, error states, immediacy of changes, and permission requirements. It is adequate but leaves notable 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?

With schema description coverage at 0%, the description fully compensates by listing all three parameters, their allowed values (action: add/remove/set_role/list, role: admin/engineer/operator), and usage notes (email ignored for 'list', default role). This adds complete meaning beyond the bare schema.

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: 'Add, remove, or update a team member' and 'Manages team seats and role assignments'. It is a specific verb+resource combination that distinguishes it from the numerous printer/design-related sibling tools.

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 context on when to use by labeling it an 'Enterprise feature' and specifying tier limits ('Business tier supports up to 5 seats; Enterprise is unlimited'). It does not explicitly exclude use cases or mention alternatives, but the tier info guides usage.

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