read_messages

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states the purpose and gives no information about side effects, whether messages are marked as read, pagination behavior, or authentication requirements. This is a significant gap for a tool that reads user data.

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, front-loaded sentence with no wasteful content. It is concise and to the point, although its brevity means it lacks supporting details. It earns a high score for conciseness but not perfect because it is under-specified.

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 absence of annotations and an output schema, the description is incomplete. It does not explain what the tool returns, how conversations are selected, or any side effects. Users would need to infer the behavior from the parameter names, which is insufficient for effective tool selection and invocation.

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 provides 100% coverage of parameters with clear descriptions, including default behaviors for max_conversations and max_messages_per_conversation. Since the schema already documents the parameters thoroughly, the description is not required to add more, so 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 uses the specific verb 'Read' with the resource 'LinkedIn messages/conversations,' clearly stating the tool's function. It is easily distinguished from sibling tools like send_message and read_feed, which involve different actions or content types.

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 no guidance on when to use this tool versus alternatives. It does not mention scenarios where reading messages is appropriate, nor does it exclude other tools or mention any prerequisites, such as requiring an active login session.

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