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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is known. The description adds only the scope word "single" — it says nothing about not-found behavior, visibility/permission constraints, or whether draft content includes unpublished media references. Adequate but thin for a tool whose annotations do most of the disclosure.

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 front-loaded sentence with zero waste; nothing is buried. It is arguably too terse to earn a 5, since brevity here comes at the cost of any usage or error guidance.

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?

The tool is a one-parameter read with an output schema and full annotation coverage, so the description does not need to explain return values or safety. What remains missing is minor: not-found behavior and how the id is obtained (the schema covers the latter).

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 parameter's schema entry even points at list_drafts as the source of the id. The description only restates "by id" and adds no format, validity, or sourcing semantics beyond 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 ("Fetch") and resource ("LinkedIn post draft") with the singular scope ("a single ... by id"), which distinguishes it from list_drafts and create_draft without ambiguity. It does not explicitly contrast with get_post or get_comment_draft, so no credit for named sibling differentiation.

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?

Usage is only implied: an agent infers it should call this when it already has a draft id and needs the full record rather than a listing. There is no explicit statement of when to prefer it over list_drafts, nor any note about what happens for an invalid or deleted id.

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