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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral context beyond annotations: it specifies 'active' memberships (implying filtering by status) and 'for one Talent CRM pool' (scoping to a single pool). These are useful details not present in the annotations, providing additional insight into the tool's behavior.

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 wasted words, and the key action is front-loaded ('List active prospect memberships'). It is appropriately concise for a simple operation, though it could be slightly more informative without becoming verbose. The structure is clear and to the point.

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 there is no output schema and the schema has 4 parameters with 0% description coverage, the description is incomplete. It fails to explain pagination parameters, the required pool_id, or what constitutes an 'active' membership. For a list operation, an agent would need to know how to handle limits and cursors, which are absent. The description covers only the basic action, 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 information about any of the four parameters (limit, pool_id, request_id, starting_after). It does not mention that pool_id is required, nor does it explain pagination (limit/starting_after) or the purpose of request_id. With low coverage, the description must compensate but fails to do so, leaving parameters entirely unexplained.

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 verb 'list', the resource 'prospect memberships', and the scope 'for one Talent CRM pool'. It distinguishes from siblings like talent_pool_members_add and talent_pool_members_remove, and from talent_pools_list (which lists pools, not members). The purpose is unambiguous.

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 usage is implied by the description: you call this to list members of a specific pool. However, there is no explicit guidance on when to use this vs alternatives (e.g., when you need all members vs. active ones, or when to use a different listing tool). The description doesn't mention exclusions or alternative conditions, so it relies on the agent to infer the appropriate context.

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