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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds the substantive content of the response (limits, formats, guidelines), but says nothing about whether rules vary per platform, how fresh they are, or auth requirements — modest added value against an already-covered safety profile.

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?

A single front-loaded sentence naming the return payload and its three components, with no filler, preamble, or redundancy. Every clause earns its place.

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?

An output schema exists, so the description need not enumerate return fields, and annotations cover the read-only safety stance. The only gap is the absence of any usage context (e.g., call before drafting/publishing), which for a simple zero-param getter is a minor omission rather than a blocking one.

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?

The tool takes zero parameters, so per the baseline there is no parameter semantics for the description to explain. It correctly does not invent parameter behavior, leaving the empty schema to speak for itself.

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 ('Returns') and a well-defined resource ('platform publishing constraints'), then enumerates the content: character limits, media format requirements, guidelines. No sibling tool in the list retrieves rule/constraint data, so the distinction is implicit, but the description never names an alternative to make it explicit.

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 can infer this should be consulted before drafting or publishing, but the description never says when to call it, whether it must precede autoposter_draft_post/publish_draft, or that it is platform-scoped. No exclusions or alternatives are given.

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