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

Annotations already tell the agent this is a non-read-only, non-idempotent, non-destructive operation. The word 'Queue' usefully signals asynchronous/background processing rather than a synchronous result, which is genuine added context. However, it never says whether existing voice data is replaced, what approvals/limits apply (rate limits, cost), or that repeat calls queue duplicate work despite idempotentHint=false.

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?

A single front-loaded sentence with no filler; the operation and its scope come first. It is arguably too terse for the behavioral gaps, but the structure itself is efficient.

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?

An output schema exists, so return values need not be described. But for a queuing/mutation tool with no usage guidance and half the parameters undocumented, the definition leaves real gaps around when to invoke it and how its identity-selection parameters interact.

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 coverage is only 50% and the description adds no parameter-level meaning beyond the schema; googleAccountId is undocumented in both places. The description's mention of 'an identity visible in the workspace' loosely frames the identity selection, but doesn't clarify the identityId/googleAccountId/linkedinAccountId alternatives that the schema partially explains.

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?

Specific verb+resource: 'Queue voice re-extraction for all LinkedIn accounts linked to an identity.' An agent can tell this triggers a voice-profile re-extraction rather than a generic refresh. It does not name or contrast any sibling (e.g. edit_identity, refresh_leads), so it stops short of 5.

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 when-to-use, prerequisites, or alternatives are given. Nothing explains why you'd re-extract voice versus editing the identity directly via campaignstack_edit_identity, nor what state the identity must be in. Usage must be inferred entirely from the name.

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