linkedin_export_conversations

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 agent knows this is a safe read operation. The description adds the context of optionally including full message history, which hints at a potentially heavier operation, but does not disclose performance impacts, rate limits, or output handling. This is minimal additional context beyond the annotations.

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 a single, concise sentence that front-loads the primary action and purpose. It lists the output formats and the optional message history without any wasted words, making it highly efficient and easy to parse.

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 no output schema and only three parameters, the description covers the core function but leaves gaps such as how the data is returned or saved (e.g., does it return a file path or the data itself?), default behavior, and potential limitations like rate limits. The annotations and schema fill some gaps, but the description alone is not fully complete for an agent to understand all invocation nuances.

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 67%, with descriptions for limit and includeMessages, and an enum for format. The description summarizes the format options and mentions full message history, but these are largely redundant with the schema. It does not add new meaning for the limit parameter, so the added value is marginal.

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 exports conversations, optionally including full message history, to JSON, CSV, or Markdown. The verb 'export' plus the resource 'conversations' and the explicit output formats make the purpose unmistakable and distinguish it from sibling tools like get_conversations or search_conversations.

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 implies usage for exporting conversation data to files, but does not explicitly state when to use this tool over alternatives such as get_conversations or search_conversations. There is no mention of exclusions or specific scenarios, so the agent must infer the appropriate context from the tool name and description.

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