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

Annotations only establish that this is a safe, idempotent read; the description adds the full state machine (draft/pending/posted/failed/cancelled) with the operational meaning of each, plus what failure_reason and failure_code represent. This is behavior beyond the annotations and beyond a bare fetch description.

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?

Front-loaded with the action and resource, and every clause carries information. The middle status-enumeration sentence is long but each state's implication earns its place; minor tightening possible but no dead weight.

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 an output schema present and annotations covering safety, the description supplies the remaining interpretive context an agent needs: the state lifecycle and what to check before reporting success. Nothing essential for correct invocation or interpretation is missing.

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% and the single id parameter is already fully documented in the schema, including its provenance (from list_comment_drafts or create_comment_draft). The description adds no additional parameter meaning, so the 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 and resource: 'Fetch a single LinkedIn comment draft by id.' An agent can immediately separate this from siblings like get_draft, list_comment_drafts, or update_comment_draft without opening any schema.

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 clear workflow trigger: use this to 'confirm what a commit actually did' and read it 'before telling the user a committed comment is live.' That is strong when-to-use guidance, though it never names the alternative (e.g., list_comment_drafts for enumeration) or states when-not to call it.

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