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

Goes beyond the readOnly/idempotent annotations by disclosing partial-result behavior: a network may still be scheduled or have waiting_for_url set, in which case the agent should report that and offer to re-check. Also instructs not to invent URLs, which prevents fabrication of missing permalinks. It doesn't specify an error/not-found path or whether results are cached, keeping it just short of a 5.

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-loads the purpose sentence, then a when-to-use line, then three tight bullet constraints. Slight redundancy between the intro's network list and the Threads note, but every bullet adds operational value.

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?

For a single-parameter read tool with no output schema, the description covers trigger conditions, parameter provenance, partial-result handling, and output presentation (show each URL as a clickable link). Nothing an agent needs to call and interpret it correctly 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 coverage is 100% and the sole post_id parameter is already documented as the `_id` from schedule_post, cross_post, or get_scheduled_posts. The description restates that provenance but adds no format or validation detail beyond the schema, so the baseline of 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 (return the public URLs for a post) and enumerates the six networks covered. This distinguishes it clearly from sibling tools like get_scheduled_posts and cross_post, which produce posts rather than retrieve their permalinks.

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?

Explicitly names the triggering conditions (user asks for the link/permalink after posting, or schedule_post/cross_post returned no URL) and gives the Threads caveat as a concrete example. It also states where the post_id comes from, so the agent knows the prerequisite call chain.

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