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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds valuable context that this only records a copy event and does not send anything, but it does not explain what state is destroyed, whether repeated calls create duplicate events, or what the response contains.

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?

Two short sentences with no filler; the recording action is front-loaded and the ownership clarification follows it. Nothing repeats the title or wastes the agent's attention.

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?

There is no output schema and no annotations guidance beyond hints, and the single parameter is undocumented in both schema and description. For an event-recording mutation the description should at minimum identify what messageId refers to and whether the call has side effects beyond logging.

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 0% and the description never mentions messageId. With a single required parameter the agent gets no hint whether it is the LinkedIn draft ID, the lead's message ID, or an activity record ID — the one field the tool needs is entirely unspecified in prose.

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?

States a specific verb and event: 'Record that the owner copied a LinkedIn draft.' The second sentence implicitly distinguishes it from sending tools like soclo_leads_linkedin_sent by clarifying the owner sends messages themselves, though it never names that sibling explicitly.

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 context of use is implied (call this after the owner copies a draft) but there is no explicit 'use this when / not when' guidance. The clarification that the owner sends LinkedIn messages themselves hints the tool does not send, but the agent must infer that from the sibling list rather than from stated exclusions.

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