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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the field scope (including a list move) but does not disclose overwrite semantics for a destructive operation—e.g. whether omitting a field clears it or whether setting 'note' replaces existing content—which is the key behavioral risk here. No contradiction with annotations.

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?

Two sentences, purpose front-loaded, and the terminology clarification earns its place. The field enumeration is dense but relevant; nothing is padding, though it could be tightened.

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 mutation tool whose destructiveHint is already carried by annotations and which has no output schema, the description adequately covers purpose and mutable field scope. The gaps are the overwrite/clearing behavior and coverage of the remaining undocumented parameters, which are meaningful but secondary given the low annotation-implied burden.

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 only 24%, so the description must compensate and does partially by mapping categories to fields (name→firstName/lastName, title→title/jobTitle, LinkedIn URL→profileUrl, list move→listId, note). But the vague 'profile metadata' lump and the unmentioned 'intent' (and position, connectionDegree, sourcePostUrl) leave several of the 17 params unexplained in both places.

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+resource ('Update an existing LinkedNav contact') and usefully disambiguates the domain terminology (lead/prospect). It distinguishes the operation from create_contact or delete_contact implicitly, but it does not explicitly route against the large sibling set (e.g. bulk_move_contacts, add_lead_to_campaign).

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 word 'existing' implies updating a record that already exists rather than creating one, which is a hint at when to use it. However, there is no explicit when-to-use vs alternatives guidance, no exclusions, and no mention of the many siblings that could move a contact or enrich it.

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