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

readOnlyHint already declares the safety profile, but the description adds meaningful behavior beyond annotations: the data source (imported LinkedIn export), the ordering (oldest first), the returned fields (who sent each message plus full text), and the ambiguity fallback (returns candidates to choose from when a name matches several people). It does not mention pagination or result-size behavior, keeping it below 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?

Front-loaded with the core action, then usage examples, then the argument and ambiguity note. Each sentence earns its place, though the example-heavy middle sentence is slightly dense and could be trimmed.

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?

There is no output schema, yet the description usefully previews the return contents (per-message sender and full text) and the disambiguation behavior, which is what an agent needs. Missing only edge-case handling like what happens when no conversation exists or how limit interacts with the oldest-first ordering.

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 both parameters (person, limit) are already documented in the schema. The description restates 'Pass a name or a LinkedIn profile URL' and the ambiguous-name behavior but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 ('Read the user's LinkedIn message history (DMs) with one person') and adds scope (one person, imported export), ordering (oldest first), and contents (sender + full text). An agent can distinguish this from search_linkedin_messages, which is query-based rather than thread-based, without opening either schema.

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 concrete usage contexts ('what did I message Sander?', 'did she ever reply?', 'before drafting a follow-up'), which is clear when-to-use guidance. It stops short of naming when NOT to use it or pointing at the obvious alternative search_linkedin_messages, so it is not a full 5.

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