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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description earns credit by disclosing a non-obvious behavioral trait: a 'partial' outcome means some channels succeeded, and republishing would duplicate them. That is decision-relevant context beyond the annotations.

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 compact sentences, no filler, with the data description front-loaded before the operational caution. The opening noun fragment is slightly awkward but nothing is wasted.

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 carries the return-value burden and does describe the shape (post, per-channel outcome, public link) plus a downstream warning. For a single-resource read tool this is essentially complete; only the input parameter is left 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 description coverage is 0% and the description never mentions the sole parameter. The parameter (postId) is self-evident and required, so the cost is low, but the description does nothing to 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?

The description names the resource and the payload precisely ('The post and its per-channel outcome, with the public link'), so an agent knows what comes back. It is a noun-phrase fragment with no explicit verb and does not distinguish itself from lookalike siblings such as post_results or list_posts, so it stops short of a 5.

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 caution 'Read targets, not just status: partial means some channels succeeded and republishing everything would duplicate them' implies a when-to-use context (before republishing), but no alternative tool is named and no explicit when-not is given. Usage is inferred rather than stated.

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