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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful scoping fact that only unscheduled drafts are returned, but says nothing about pagination, ordering, or how the limit interacts with a large draft list.

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 purpose is front-loaded in the first clause and the description is only two sentences. The second sentence is long and packs several backticked field names, but every element is relevant to using the tool.

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 enumeration of platforms/channelNames/content/dashboardUrl is largely redundant, though the client-side filtering hint is genuinely additive. For a simple read tool with annotations, this is adequate but leaves the only input parameter fully unexplained.

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 single `limit` parameter (default 20, max 100) is never mentioned in the description, so its meaning and pagination behavior are undocumented in both places. The field-level detail provided is about response fields, not input parameters, so it does not compensate for the 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?

States a specific verb and resource ('List the user's draft posts') and scopes it with '(not yet scheduled)', which implicitly separates it from list_scheduled_posts. It never names a sibling tool explicitly, so the differentiation is inferential rather than stated.

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 one concrete usage instruction: filter client-side via platforms/channelNames when the caller wants a specific platform or account. It offers no guidance on when to prefer this over get_post, search_posts, or list_scheduled_posts, and no exclusions or prerequisites.

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