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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation and idempotency profile is covered. The description adds that the prospect must already exist but does not disclose behaviors such as duplicate handling, failure modes, or what happens to associated data.

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 sentence with no superfluous words. The action is front-loaded and the phrase 'existing prospect' adds meaningful context without bulk.

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 simple add operation, the description covers the core action, but with no output schema and two undocumented optional parameters, the agent is left unsure about the meaning of request_id and idempotency_key and about the expected result of the call.

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 the parameters. While pool_id and prospect_id are inferable from the wording, request_id and idempotency_key receive no explanation, leaving a material gap for a tool with four parameters.

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 uses a specific verb ('Add') and resource ('existing prospect to a Talent CRM pool'), clearly distinguishing the add operation from sibling tools like yardstick_talent_pool_members_list and yardstick_talent_pool_members_remove. It is immediately obvious what this tool does.

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 usage by naming the action and resource, and the word 'existing' narrows eligibility. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any preconditions or exclusions beyond the implicit 'existing prospect'.

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