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

Annotations already cover read-only and open-world traits, so the description only needed to add context; it does mention 'Returns a list' and pagination. However, the instruction 'use cursor when paginated' is misleading because the input schema defines no cursor parameter — only offset/limit/pageSize/maxResults described as possibly ignored. This is unactionable guidance that conflicts with the actual schema contract.

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 short sentences with the purpose front-loaded and no filler. The minor grammatical error 'a entity id' and the vague pagination clause are the only blemishes; otherwise it is efficiently sized.

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 11 parameters, no output schema, and no enums, this description is under-specified. It does not explain what 'grouped' means, which entity-id parameter to prefer (entityId vs entity_id alias), how pagination actually operates given no cursor parameter exists, or what the response shape looks like. An agent would need to guess at invocation details.

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 baseline 3 applies. The description adds little beyond the schema: 'Accepts a entity id' is redundant with entityId's own description ('LinkedIn person entity ID. Not a vanity handle.'), and the cursor pagination note does not map to any actual parameter. It neither clarifies the degenerate 'Ignored if this tool does not support it' pagination params nor compensates for the schema's ambiguity.

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 ('Get grouped employment history for a LinkedIn person') that is clearly distinct from sibling person tools like person_posts, person_interests, and person_recommendations. 'Grouped employment history' is a specific data type that disambiguates well, though it does not explicitly name the siblings it is not.

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?

No guidance on when to use this tool versus alternatives such as linkedin_live_profile_get_v2 or person_recommendations, and no mention of the prerequisite that an entity ID is needed (or that person_resolve can produce one). The description merely states it accepts an entity id, leaving selection and invocation conditions to inference.

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