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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating operation, and the description's 'Record' is consistent with that. But the description never says what actually changes on the lead record — whether the lead stage advances, activity history is appended, or follow-up automation is affected — which is especially important given the surprising destructiveHint=true for what sounds like a simple event log.

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?

One short sentence with the action front-loaded and no filler. It is efficient, though the brevity borders on under-specification rather than true conciseness.

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?

This is a mutating tool with no output schema, one completely undocumented required parameter, and an unexplained destructiveHint=true. The description supplies none of the surrounding context an agent would need to invoke it confidently, such as what the messageId references or what side effects recording triggers.

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 at all, so the agent gets no help understanding whether it refers to an internal lead message record, a LinkedIn thread, or something else. For a single required UUID with an opaque name, the description needed to explain the identifier's origin but does not.

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 ('Record') and a specific event ('owner sent a LinkedIn message themselves'), which is clearer than the title alone due to the 'themselves' qualifier implying manual, non-automated outreach. However, it does not distinguish this from the closely related sibling soclo_leads_linkedin_copied, leaving the agent to guess which recording endpoint applies.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g. must the lead exist, must the message be logged elsewhere first), and no mention of alternatives such as soclo_leads_linkedin_copied or soclo_leads_outcome. The only signal is the implied context of post-manual-outreach logging.

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