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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent, not open-world). The description adds genuinely non-obvious behavior: the message is staged and not actually sent until confirm_action runs after the user agrees in chat. That two-phase commit detail is exactly the kind of context annotations cannot convey. It stops short of describing the response payload or error cases.

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, no filler, and the most decision-relevant fact (deferred send via confirm_action) is placed up front after the action statement.

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 two-parameter mutation tool with no output schema, the description covers the critical behavior an agent must know: nothing is sent until confirmation. Remaining gaps (what the tool returns, whether it overwrites an existing draft) are minor given the tool's simplicity.

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 50%: body is documented ('Exact reply text to send') while thread_id has no description in the schema or in the description text. The phrase 'reply from Inbox' weakly implies thread_id identifies an inbox conversation, but no format or source guidance is given, so the description does not compensate for the coverage gap.

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 (prepare sending) and resource (LinkedIn or email reply from Inbox), and clarifies the operation is a staging step rather than a send. It does not, however, distinguish itself from the sibling draft_reply, which an agent could easily confuse with this tool.

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 the usage context by tying the tool to a follow-up confirm_action call after user agreement, which is useful sequencing guidance. It never states when to prefer this over draft_reply, nor any preconditions such as needing an existing thread.

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