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

Annotations already declare destructiveHint=true and idempotentHint=true, covering the core safety profile. The description adds only the qualifier 'active' but does not disclose consequences (e.g., permanence of removal, effect on prospect data) or permission requirements. It does not contradict annotations.

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, brief sentence with no filler or redundant phrasing. It is front-loaded and wastes no words, though it is terse enough to lack important context.

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 that this is a destructive operation with zero parameter description coverage and no output schema, the description is too sparse. It does not explain which parameters are needed, what happens when a membership is removed, or any side effects, leaving significant gaps for correct invocation.

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 provides no explanation for pool_id, prospect_id, or request_id. It fails to compensate for the schema's lack of semantic detail, leaving the agent to infer parameter meaning solely from names and requiredness.

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 verb ('Remove') and resource ('active prospect membership from a Talent CRM pool'), making the tool's purpose clear. It is distinct from sibling tools like yardstick_talent_pool_members_add and yardstick_talent_pool_members_list based on the verb, though it does not explicitly name or contrast them.

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 provided on when to use this tool versus alternatives, prerequisites, or conditions for removal. The description only restates the action without explaining context, such as when a prospect should be removed or how this relates to add/list operations.

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