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

Annotations already cover read-only safety. The description adds useful behavioral detail: subscription requirement, most-recent message selection via message_count, and the total_message_count comparison for detecting that more messages exist. It does not detail pagination mechanics or error handling, but it is informative for typical use.

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 description is compact and each sentence adds a distinct piece of information: what is fetched, subscription requirement, where the ID comes from, and how message_count behaves. No filler or redundancy.

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?

Covers the key prerequisites, parameter source, return contents, and message_count semantics. It does not explain pagination or failure modes, but for a read-only fetch tool this is not critical. The 'all its messages' phrase undercuts precision but the subsequent message_count/total_message_count explanation compensates.

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?

The schema already documents all three parameters (account_id, thread_id, message_count), so the baseline is 3. The description adds real value by specifying where thread_id comes from and clarifying that message_count limits the most recent messages and can be compared against total_message_count. This goes beyond simple schema descriptions.

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 identifies a specific fetch operation, the resource type (Sales Navigator thread), what it returns (messages and participant profiles), and names the endpoint(salesApiMessagingThreads/{id}). It also distinguishes the operation from send/list tools. Slight inconsistency: it says 'all its messages' but then explains message_count limits the number of returned messages.

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 a clear prerequisite (Sales Navigator subscription), gives the provenance of thread_id (from salesnav_list_messaging_threads), and explains message_count behavior. It does not explicitly compare to a sibling alternative (e.g., when to use another listing tool), but the invocation path is clear enough.

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