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

No annotations are provided, so the description must carry the behavioral burden. It discloses the key effect (draft discarded, nothing sent to LinkedIn) and mentions a 200 success response, but omits irreversibility, permissions, and whether the draft can be recovered.

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?

The action is front-loaded and the body is short. The repeated title and generic response/content-type boilerplate add little value, but do not obscure the core instruction.

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 one-parameter tool, the core invocation and no-send side effect are covered. Without annotations or an output schema, however, auth requirements, irreversibility, and detailed return behavior remain undocumented.

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 coverage is 0%, but the description compensates for the single parameter by explaining its source and prefix: 'draft_ handle from list_drafts.' This adds useful meaning beyond the bare 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 uses a specific verb ('discard') and resource ('connection-note draft') and explicitly says it is not sent. This clearly separates it from approve_draft and from skip_comment_draft, skip_content_draft, and skip_reply_draft siblings.

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?

It gives a clear usage context: discard an unsent draft and source the handle from list_drafts. However, it does not explicitly name alternatives such as approve_draft or state when not to use this tool.

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