wetrack_add_client_members

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

There are no annotations, so the description carries the full burden of behavioral transparency. It states that the operation assigns or updates members, but it does not disclose whether existing members are overwritten, whether members are added incrementally, or what side effects occur for removed associations. For a mutation tool, this ambiguity is a meaningful gap.

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 compact and front-loaded with the primary purpose, followed by a scannable Args block. There is minimal redundancy, though 'client_id: The client ID' is somewhat tautological. Overall, it earns its space without excessive prose.

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 two-parameter mutation with an output schema, the description is nearly sufficient, but the ambiguous assign/update behavior leaves an important gap. An agent cannot determine whether the tool replaces the entire member set or appends to it, and there is no note about prerequisites or side effects. The output schema reduces the need to describe return values, but behavioral context is still missing.

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%, so the Args section is the only source of parameter meaning. It adds basic semantics and an example for member_ids ([1, 2, 5]), but client_id is only described as 'The client ID', which adds little beyond the schema. It does not clarify whether member_ids must reference existing users or whether passing an empty list has any effect.

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 (assign/update) and the resource (client members), which makes the tool's scope evident and helps distinguish it from wetrack_update_client and other client-level tools. The 'members' qualifier is specific enough that an agent can tell what resource is being affected. It is slightly vague about whether 'update' means replacing or appending, but the core purpose is clear.

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?

No guidance is given for when to use this tool versus alternative client-management tools such as wetrack_update_client or wetrack_create_client. The description does not mention whether this tool is appropriate for replacing the full member list, appending members, or removing members via an empty list. An agent must infer usage from the tool name and description alone.

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