linkedin_reply_to_conversation

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

Beyond the annotations (readOnly=false, destructive=false), the description adds no behavioral details such as side effects, required permissions, or error conditions. The only extra context is 'by its id', which is parameter semantics rather than behavior. With annotations already indicating a non-read-only, non-destructive action, the description contributes little.

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?

A single, concise sentence that immediately conveys the tool's purpose with no filler or redundant content.

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?

For a simple two-parameter mutation tool with annotations and full schema coverage, the description is complete enough. It explains the core action and identifies the target conversation. No output schema exists, so return values are not described, but that is not a significant gap.

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 fully describes both parameters (conversation, text) with 100% coverage. The description's mention of 'by its id' reinforces the conversation parameter but adds no new detail beyond the schema.

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 verb ('Send') and resource ('message into an existing conversation thread'), and specifies it operates by the thread's id. This distinguishes it from sending new messages (e.g., linkedin_send_message) by emphasizing 'existing conversation thread'.

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 that this tool is for replying to an existing conversation thread, but provides no explicit guidance on when to use it over related tools like linkedin_send_message or linkedin_manage_conversation. No alternatives or exclusions are mentioned.

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