linkedin_manage_conversation

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

The description explicitly states that deletion is irreversible and removes the thread from the user's inbox only, which is critical destructive behavior. However, the annotations declare destructiveHint=false, directly contradicting the description. This is a serious inconsistency that undermines the agent's ability to assess the tool's safety.

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 two sentences long, front-loaded with the action list, and each sentence carries meaningful information. No wasted words.

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 moderate complexity, the description covers the main actions and the critical consequence of deletion. There is no output schema, but none is strictly needed. A minor gap is the lack of mention of permissions or errors, but overall it is sufficiently complete.

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 input schema already provides 100% description coverage for both parameters (action with enum values, conversation with id/URN/URL). The description adds no additional parameter semantics, so the baseline of 3 applies.

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 purpose with specific verbs and resources: 'Archive, unarchive, mark read/unread, or delete a conversation.' It enumerates the exact actions and distinguishes itself from sibling tools like send_message or get_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 when to use the tool (for managing conversation state) but lacks explicit guidance on when not to use it or how it compares to alternatives. For instance, it doesn't mention that sending messages should use linkedin_send_message or that viewing history should use get_conversation_history.

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