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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds that results span LinkedIn and email and are 'recent', but never defines the recency window, ordering, or result limits.

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 short sentences with the resource stated first and the optional refinements second; nothing is wasted, though the phrasing is terse to the point of underspecification.

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 3-parameter read-only list tool with no output schema, an agent still lacks the meaning of 'recent', the ordering of results, and what the non-obvious filter enum values do. Adequate as a minimum but with clear gaps.

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 0%, so the description carries the burden and it only partially compensates: 'search' loosely maps to query, 'unread filter' to filter, and the channel list to channel. The enum values 'positive' and 'meeting' for filter are left completely unexplained, and no parameter formats are given.

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?

The description gives a clear resource ('LinkedIn and email conversations') with an implied list verb and names the two channels covered. It doesn't differentiate itself from siblings like get_thread, which also deal with inbox conversations, but the resource is specific enough for selection.

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?

'Optional search and unread filter' hints at what can be narrowed but never states when to call this instead of get_thread or search_prospects, nor any prerequisite such as connection/auth state. No when-not guidance at all.

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