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

Adds substantial context beyond the annotations (readOnly=false, idempotent=false, openWorld=true): the queue-wait semantics, business-hours dependency, that limits/pauses/disconnected accounts override priority, and a precise credit model (existing URL free, identity finding charged only on success). Those cost and throttling disclosures are exactly what an agent needs before spending the user's credits.

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?

Front-loaded with the action and the 50-profile limit, then the priority rules, then the caveats and cost note — a sensible information order. The single dense paragraph is efficient, though the priority clause is packed tightly enough that it takes a second read.

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?

With an output schema present, return values need no explanation, and the description covers the remaining agent-relevant concerns: queue timing, priority thresholds, throttling, and credit cost. The only absent piece is sibling differentiation, which is a routing concern rather than a completeness gap in calling this tool 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?

The priority enum is explained in depth and the 50-item cap is stated, both mapping to schema fields. But schema description coverage is only 40%, and the description says nothing about the 'results' item shape (required profileUrl, the global/private leadSource enum, why optional identity fields like fullName or headline would be supplied) or about campaignId. It partially compensates but leaves real gaps.

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?

States a specific verb and resource with a hard scope limit: 'Queue up to 50 LinkedIn lead profiles for fresh enrichment.' An agent immediately knows this is an async enrichment-queueing operation rather than a read or an edit. It does not, however, distinguish itself from the sibling campaignstack_enrich_leads, which an agent could plausibly confuse it with.

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?

Gives clear within-tool routing guidance: 'normal' vs 'high', including the concrete threshold of up to 5 profiles for immediate reading and the 'like opening the profiles yourself' analogy. It also warns that daily limits, pauses and a disconnected account still apply. It stops short of naming when to prefer this over campaignstack_enrich_leads or campaignstack_get_lead_refresh_status.

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