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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral context: the Sales Navigator subscription requirement and the pagination mechanism (passing next_page_starts_at as page_starts_at). This goes beyond what annotations provide, though it doesn't discuss rate limits or auth specifics, which is acceptable for a read-only tool.

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 sentences with no verbosity, front-loaded with the purpose, then requirement, return contents, and pagination. Every sentence adds essential information, and the structure is logical and efficient.

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?

Given the tool's simplicity, presence of an output schema, and full parameter descriptions in the schema, the description covers the key aspects: purpose, requirement, return type, and pagination. It doesn't mention the filter options or count parameter, but those are already well-documented in the schema. It is complete enough for correct invocation; a 4 reflects minor gaps like not mentioning that it returns threads for the given account only.

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 all parameters are already documented. The description reinforces pagination semantics ('Paginate by passing next_page_starts_at from the previous response as page_starts_at'), but this largely mirrors the schema's own description for page_starts_at. It does not add new meaning for count or filter, so the 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?

The description clearly states the tool's function: listing Sales Navigator messaging threads, with the internal resource name (salesApiMessagingThreads) and return contents (threads with messages and participant profiles). This distinguishes it from sibling tools like list_conversations (regular LinkedIn messaging) and salesnav_list_thread_messages (messages within a thread), even though alternatives are not explicitly named.

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?

The description provides a prerequisite (Sales Navigator subscription) and pagination instructions, but does not explicitly state when to use this tool over alternatives like list_conversations or salesnav_list_thread_messages. The Sales Navigator scope is implied by the name, but no explicit 'when not to use' or alternative routing is given.

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