add_workspace_member

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

No annotations provided, so description carries full burden. It discloses that certain roles are automatic and workspace_billing cannot be assigned. However, it does not mention the confirmation mechanism or any other behavioral traits like permissions or side effects.

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?

Three concise sentences with no fluff. The first sentence clearly states the purpose, and the following sentences add essential context. Every sentence is justified.

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?

Has output schema (not shown but available). The description covers the main purpose, exceptions, and a behavioral constraint (workspace_billing inherited). It lacks mention of the 'confirm' parameter's role, but overall is sufficiently complete for a simple add operation.

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 50% (workspace_role and confirm have descriptions). The description adds context about roles (workspace_billing cannot be assigned) but does not describe workspace_id or user_id semantics. It partially compensates for the schema gap.

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 verb 'Grant' and the resource 'user access to a workspace'. It distinguishes from siblings like 'invite_member' by implying direct addition, but does not explicitly differentiate from 'invite_member' or 'update_workspace_member_role'.

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?

Provides explicit context: org admins and billing members get automatic roles and don't need to be added, and workspace_billing role is inherited. This guides the agent on when not to use the tool, though it does not mention when to prefer this over 'invite_member'.

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