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

The description only notes that the person must already exist. It does not explain the 'confirm in Yardstick' behavior suggested by the title, nor what happens on duplicate membership, what side effects occur, or what the response looks like. Annotations indicate idempotent and non-destructive, but the description adds little behavioral context beyond that.

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, economical sentence with no filler and is appropriately front-loaded. It is concise, but it omits important context carried by the title, so it is not as complete as it could be while still being short.

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 four-parameter tool with no output schema and no parameter descriptions, this description is too thin. It clarifies the two required identity parameters at a basic level but leaves the optional request_id and idempotency_key unexplained, and the title's confirmation workflow is never addressed. An agent has enough to attempt a basic call but not to use the tool fully and correctly.

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 description must compensate. It weakly maps 'person' to person_id and 'Department' to department_id, but says nothing about request_id or idempotency_key. An agent cannot understand the meaning or purpose of two of the four parameters from the description alone.

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 and target: 'Add an existing person to a Department.' This distinguishes it from related member operations like remove and set_lead, though it does not explicitly name a sibling for comparison. The title's parenthetical 'confirm in Yardstick' introduces an ambiguous workflow element that the description does not clarify.

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 on when to use this tool versus alternatives such as departments_members_remove, departments_members_list, or talent_pool_members_add. There is no mention of prerequisites, such as verifying the person exists or whether the department must already be set up. The intended use is only implied by the name and one-line description.

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