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

With annotations only declaring write/open-world/non-destructive, the description adds the substantive traits: the write lands in Sales Navigator itself (removal must happen there, not via this tool), a seat is required, and it consumes a 100/day allowance. These are exactly the constraints an agent can't infer from structured fields.

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?

Three tight sentences, front-loaded with the action and scope, followed by prerequisites, id format, state location, and quota. Every sentence carries information the agent needs.

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?

No output schema exists, so the description should cover outcome and side effects; it does state where the lead lands and how to undo it. The only remaining gap is the lack of contrast with the create_lead/create_leads_bulk siblings.

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%, so baseline is 3. The description adds id provenance (ACw prefix, comes from a search_linkedin sales_navigator result or lead URL), which is mildly useful, but says nothing about listId or connectionId beyond what the schema already documents.

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 ('Save ONE person as a lead in your Sales Navigator') plus optional list targeting, and the capitalized 'ONE' implicitly contrasts with the bulk sibling. It never names create_lead or create_leads_bulk, so an agent facing both create_lead and save_lead gets no explicit disambiguation.

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 preconditions: a Sales Navigator seat is required, and the lead must be an ACw… id sourced from a search_linkedin sales_navigator result or a lead URL. That effectively routes the agent to the right lookup tool first. It does not state when to prefer this over create_lead/create_leads_bulk.

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