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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds real context beyond that: the default result set is upcoming posts only, and past posts are surfaced with their outcome when requested — a behavioral distinction the annotations cannot convey.

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 compact sentence with the default behavior front-loaded. The fragmentary 'Scheduled posts:' opener is slightly clipped but costs no reading time.

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?

With no output schema and no annotations-level safety gaps, the description plus schema is nearly sufficient. However, 'their outcome' is left unexplained (what fields past posts return), which matters for an agent deciding whether to query past statuses.

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%, including enum values and limits, so the schema does the heavy lifting. The description only reinforces the status semantics ('past ones and their outcome') without adding format or default details beyond what the schema states.

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?

Names the resource (scheduled posts) and the default scope (upcoming), and distinguishes the alternate mode (past posts and their outcome). The verb is only implicit through the title, and no sibling is named, so an agent must infer that this is the list operation rather than a get/action tool.

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 default-versus-past distinction implies when each mode applies, but no explicit when-to-use guidance or alternatives (e.g. list_pending_actions, get_attention_items) are given. An agent can guess intent from the status enum but the description doesn't route it.

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