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

Annotations only indicate non-read-only and non-destructive, but the description adds valuable behavioral details: it enriches profiles, skips already-saved entries (idempotency), and counts against the import quota. This is useful operational context that helps the agent anticipate side effects beyond what annotations or schema provide.

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 two sentences that front-load the core purpose and then state the two most important behavioral notes (skip duplicates, quota impact). There is no waste and no redundant restating of the tool name or title.

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 tool with two simple parameters and no output schema, the description covers key operational aspects: enrichment fields, deduplication, and quota impact. It does not mention request size limits or error handling, which is a minor gap but not critical for tool selection or basic 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 100%, so the baseline is 3. The description indirectly maps the linkedinUrls parameter to the action of saving profiles, but it does not add new meaning to listId or the URL format beyond what the schema already provides. The description does not compensate further for parameter semantics.

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 tool saves LinkedIn profiles as prospects and enriches them, listing specific enrichment fields like name, role, and company. It distinguishes the tool's input type (URLs) from sibling tools, though it doesn't explicitly name alternatives like import_sourced_leads. Overall it is a specific and understandable purpose.

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 the tool should be used when you have LinkedIn URLs to save as prospects, but it does not mention when to prefer it over sibling tools such as import_sourced_leads. There are no explicit exclusions, prerequisites, or conditions that would help an agent choose between this and similar tools. Guidance is left purely to inference.

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