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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds valuable context by confirming no send occurs, listing what is returned, and scoping file attachment to connected LinkedIn conversations in the selected product. It omits any note on revision conflicts despite returning an 'inbound revision'.

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?

Three front-loaded sentences with the core purpose and the 'Never sends' boundary up front, and no wasted filler. The dense cluster of jargon terms ('inbound revision', 'owned file identity') slightly reduces clarity.

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?

With no output schema, the description usefully enumerates the return fields (recipient, sender, channel, revision, signed body, file identity), and annotations plus full schema coverage handle safety and parameters. The weak when-to-use routing against send_conversation_reply is the only real 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?

Schema description coverage is 100%, so the schema already documents conversation_id, body, and attachment_id with format examples. The description adds no parameter-level meaning beyond noting the booking-link tracking already present in the schema, so baseline 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?

States a specific verb+resource ('Prepare one exact local inbound reply') and immediately differentiates from the write sibling with 'Never sends'. An agent can distinguish this preview tool from send_conversation_reply without opening either schema, though the adjective 'local' is slightly jargony.

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?

Gives a usage constraint (files work only for supported connected LinkedIn conversations) and the 'Never sends' boundary, but never explicitly says when to prefer this over send_conversation_reply or get_reply_attempt. Usage is implied rather than routed.

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