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 covered. The description adds useful behavioral context: the LinkedIn limitation, the exact workflow for obtaining chat IDs, and the invalid-value caveats.

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?

The main purpose is front-loaded and the LinkedIn workflow is compactly stated. Minor redundancy exists between 'Do not use a person name as chat_id' and the final 'Never pass: person name, user_id, message_id.'

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?

With five parameters and no output schema, the description gives the main purpose and caveats but omits pagination/filter semantics and the expected return shape beyond 'chat.id'. It is minimally viable for a read-only lookup, but not fully complete for an agent to call it confidently.

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 20%, but the description does not explain limit, cursor, or is_unread; it focuses mostly on a chat_id concept that is not even an input property. The account_id guidance is already in the schema, and the provider enum is self-explanatory, so the description fails to compensate for the low coverage.

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 opens with a specific action and resource: 'List/search conversations' to map a recipient/topic to an exact chat_id. It also delineates the LinkedIn case by naming linkedin_list_inboxes and linkedin_list_inbox_chats, making it easy to distinguish from sibling resolver tools.

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?

It states when this tool is the right step ('before reading/replying or resolving message_id') and gives an explicit exclusion: for LinkedIn, use the two linkedin_list_* tools instead because account-wide chat listing is not supported. The negative guidance 'Do not use a person name as chat_id' and 'Never pass: person name, user_id, message_id' further clarifies correct use.

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