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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely new behavioral fact — results are sorted soonest-first — but says nothing about whether all schedules are returned, how the 50-item cap behaves, or what happens when nothing is queued.

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 short sentence with zero filler, and the ordering detail — the most useful thing an agent can know here — is placed immediately after the purpose. Nothing is buried or redundant.

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 one-optional-param read tool with rich annotations and no output schema, this is close to sufficient: purpose and ordering are covered. It stops short of clarifying the boundary with list_posts/list_slots and the capped result set, which are the remaining ambiguities an agent could hit.

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?

Only one optional parameter and the schema describes it fully ('How many to return, at most 50'), so the schema already carries the load. The description adds no meaning about the limit or default behavior, which is the expected baseline when coverage is 100%.

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?

Specific verb+resource: lists posts that are queued for publication, with the ordering ('soonest first') stated up front. It implicitly separates scheduled posts from published ones (list_posts), but never names that sibling, so the differentiation is inferable rather than 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?

The phrase 'waiting to go out' implies this is for pending/scheduled content, which gives an implicit cue about when to reach for it. There is no explicit guidance about when to prefer list_posts, list_slots, or get_post instead, and no exclusions stated.

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