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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely new context beyond the annotations: chronological ordering (oldest first) and the provenance of outbound entries (sent from ZenMode or typed directly on LinkedIn). It does not explain pagination behavior for limit/offset, which would have earned a 5.

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?

Effectively one front-loaded sentence that carries the scope, ordering, and content, plus a two-word safety tag. Efficient and readable; the 'Read-only.' fragment slightly duplicates the readOnlyHint annotation rather than adding new information.

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 read-only, single-resource fetch with no output schema, the description plus schema covers what the agent needs: what entity, what content, what ordering, and what safety posture. Only the return shape (entry fields) and paging semantics are left implicit, which is a minor gap.

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 75%, so most parameters are documented in the schema itself (limit default, direction enum, contact_id provenance). The description contributes nothing about the optional direction filter or paging, so there is no value added over the structured fields.

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 (Read), resource (LinkedIn conversation history), and scope (one contact, oldest first), which separates it cleanly from get_contact and search_contacts. The parenthetical content description ('what went out... and what they wrote back') further pins down exactly what is returned.

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?

Usage is implied by the noun phrase 'conversation history with one contact' and the contact_id requirement, but no sibling is named as an alternative and no when-not-to-use condition is given (e.g., use get_contact for profile fields instead). Adequate but leaves the agent to infer routing.

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