Base Wework Add Project Manager

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

With no annotations, the description carries the full burden. It discloses the key additive behavior (existing managers are preserved), but says nothing about auth prerequisites, duplicate handling, permission side effects, or idempotency, which is notable for a mutation tool.

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 a single front-loaded sentence: it states the action, target, and the critical non-destructive nuance without any filler. This is appropriately sized for the tool's complexity.

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?

There is an output schema, so return value documentation is less critical. However, the description omits when-not-to-use guidance and authentication context. Still, it is sufficient for straightforward invocation of an additive add-manager 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?

The schema has no parameter descriptions and the description adds little parameter-level meaning. An agent can infer 'users' likely lists the new managers and 'id' identifies the project, but there is no clarification of formats, whether usernames or user IDs are expected, or the role of access_token/username.

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 Vietnamese description clearly states the action ('Thêm quản lý mới' – add a new project manager) and the target resource ('dự án' – project). It also adds a key behavioral qualifier ('vẫn giữ nguyên các quản lý hiện tại') that distinguishes it from a set/replace operation, though it does not explicitly name sibling alternatives.

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 phrase 'while keeping existing managers' gives the agent an implicit usage signal: this is the additive operation, not a replacement. However, it does not explicitly state when to prefer this over sibling tools like set_project_manager or exchange_project_manager, nor list exclusions.

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