Create Membership

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states the core action and allowed role values, but does not mention behavior when the user is already a member, permission requirements, side effects, or whether the operation is idempotent. This is a mutation tool, so those gaps matter.

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 two short sentences with no redundant phrasing. It states the operation and the most important parameter constraint (allowed role values) efficiently, earning its place with no filler.

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?

The tool is simple and an output schema exists, so return-value details are not needed. Still, without annotations and with no guidance about duplicate memberships, permissions, or relation to update_membership, the description is only minimally complete. It covers the essential action but leaves behavioral and usage context underspecified.

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 0%, but the description adds meaning by specifying that role can be 'editor' or 'viewer', which is not enumerated in the schema. However, userId and boardId are left implicit; their semantics can be inferred from 'Add a member to a board', but the description does not explicitly clarify them.

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 uses a specific verb and resource ('Add a member to a board'), making the tool's purpose immediately clear. It distinguishes itself from the membership siblings (update_membership, delete_membership, get_memberships) by focusing on the 'add' 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 gives no guidance on when to use this tool versus alternatives. It does not say 'use this to create a new membership' or mention that update_membership should be used for changing roles. The usage is only implied by the word 'Add'.

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