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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds only the 'in the queue' framing and does not disclose ordering, pagination, or the fact that non-upcoming statuses (done/failed) can be returned — a gap worth noting since 'upcoming' slightly undersells the schema's status filter.

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 tight sentence with the resource front-loaded and zero filler. It is appropriately sized, though the qualifying word 'upcoming' is imprecise given the status filter supports done and failed.

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 return values need not be explained, and 100% schema coverage documents both optional params. The remaining gap is a lack of ordering/pagination context and any usage framing relative to siblings, but for a simple read-only list tool this is close to complete.

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%, so both parameters (limit with default/max, status enum) are fully documented in structured fields and the baseline is 3. The description adds no parameter detail beyond the schema and its word 'upcoming' arguably conflicts with the done/failed enum values.

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 (list) and resource (scheduled posts and drafts in the queue), which is enough to separate it from read/write siblings like get_post or create_post. However, it does not name or contrast itself with any sibling, so the differentiation is inferred from the resource noun alone.

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?

There is no statement of when to use this tool versus alternatives such as get_post (single post), list_templates, or list_accounts. No prerequisites, no exclusions, no routing guidance — the agent must infer usage entirely from the name.

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