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

Description discloses that it scrapes LinkedIn profiles, saves data onto the contact, and merges into profile_data. Annotations indicate non-destructive, idempotent, open-world. No contradictions; adds context about LinkedIn profile views.

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?

Four sentences, front-loaded with purpose, then specifics, then usage guidelines, then limitation. Every sentence adds value, no redundancy.

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 tool complexity and no output schema, description covers purpose, parameters, usage context, behavioral limits, and return value ('Returns per-contact enrichment status'). Sibling tools list is large but description sufficiently differentiates.

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 100%, and description adds meaning: explains profile_id as UUID of LinkedIn account (defaults to active), contact_ids as UUIDs of contacts, and reinforces the batch limit. Provides rationale for max 8.

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 it enriches contacts with full LinkedIn profile data, listing specific fields (headline, location, experience, etc.). It distinguishes from sibling 'search_google_xray' by positioning itself as a follow-up step.

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?

Explicitly says 'Use after search_google_xray to flesh out lightly-saved leads.' Also states batch size limit (max 8 per call) and notes that each contact is a real LinkedIn profile view, implying cost/rate limits.

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