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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is covered; the description adds meaningful behavioral detail on top – the confirm gate, that draft media and its alt text are carried along, and the like-for-like behavior with schedule_post for destination persistence. It stops short of saying the publish is irreversible or describing failure behavior.

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?

Four compact sentences, front-loaded with the action, then the confirm gate, then destination routing, then the media exclusion. No filler or redundancy; each sentence carries a distinct constraint.

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 still covers the side effects that matter (media/alt text published, confirm required, destination resolution). It omits what is returned on success/failure and whether the action can be undone, though destructiveHint partially compensates.

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 schema's destination description already spells out the personal/company URN semantics in far more detail than the description does. The description's 'optional' framing adds mild routing value but largely restates structured data, 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+resource ('publishes a saved post to LinkedIn') plus timing ('immediately'), which cleanly separates it from the sibling schedule_post. It also pins the input source ('stored on the draft by save_draft'), so an agent knows which object id to supply.

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 hard prerequisite ('Refused unless confirm is true') and an explicit exclusion ('Media is not accepted here'), plus routes destination lookup to list_destinations. It never explicitly names schedule_post as the alternative for deferred publishing, but the contrast is strongly implied by 'immediately'.

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