Base Wework Set Project Member

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

With no annotations, the description carries full behavioral burden. It does disclose the key behavior—'ghi đè' (overwrite)—which signals a destructive replacement. But it omits consequences (e.g., removed members losing access), permissions, reversibility, or idempotency, so coverage is only partial.

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, dense sentence with no filler words. It is concise and front-loads the key action and scope, though it ends up sacrificing informativeness for brevity.

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?

Given 4 parameters, 0% schema coverage, no annotations, and a mutation operation, the description is too sparse. An agent cannot determine what values to pass for id and users, nor what the overwrite semantics imply for existing members. The output schema helps but does not compensate for missing parameter meaning and behavioral detail.

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% and the description does not explain any of the four parameters. It never maps 'id' to project ID or 'users' to the member list format, so the agent must guess meanings despite required parameters. The description adds no value beyond the raw 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 states a specific action (overwrite/reset) on a specific resource (the entire project member list). The phrase 'toàn bộ danh sách thành viên' (entire member list) clearly distinguishes it from sibling add/remove/exchange tools, so an agent can tell it apart.

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 implies the tool's use case is replacing the whole member list, which contrasts with add/remove/exchange siblings. However, it does not explicitly name alternatives or state when NOT to use the tool, leaving the guidance implied rather than explicit.

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