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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), and the description goes further by disclosing return semantics: per-platform publish errors, how `retry_of`/`retries` indicate a resolved failure, and that `published_urls` only lists platforms that successfully posted. This is genuine behavioral context an agent cannot get from 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?

The opening clause is well front-loaded, but the body is one sprawling, unparagraphed run-on that mixes content rendering rules, thread handling, poll rendering, and retry semantics. The information is relevant, yet its density and lack of structure make it hard to scan for the one parameter an agent must supply.

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 shoulders the return-value burden and does so thoroughly, covering content, media URLs, threads, polls, errors, and published URL mapping. It omits only edge behavior such as an invalid or missing post ID, which is a minor gap for a single-resource getter.

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 there is a single `id` parameter already documented as 'The post ID.' The description adds no format, source, or lookup guidance for the ID, so the baseline 3 applies – the schema carries the full burden.

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: 'Get full details of a specific post' with an enumerated scope (content, channels, media, errors, retry linkage). An agent can tell this is a single-post detail fetch, not a list or analytics call, though it never names the sibling it differs from (get_post_analytics, list_posts) to sharpen the distinction.

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 via the phrase 'enough to fully verify a scheduled post without opening the dashboard.' There is no explicit when-to-use, when-not-to-use, or named alternative such as get_post_analytics for metrics; the agent must infer the boundary itself.

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