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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description reinforces it with 'Read-only' and adds the required manage:schedule scope. It goes further by explaining that 'ready' means nothing posts automatically, which prevents a real misunderstanding. It does not mention pagination limits beyond the param or ordering stability, but the lifecycle semantics carry genuine behavioral value.

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?

Front-loaded with the core purpose and default behavior, then statuses, then return shape. It is dense but long; the status glossary is justified, though the return-format sentence could be slightly tightened. Every sentence still contributes information.

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?

No output schema exists, so the description supplies the return contract itself: a numbered summary with truncated ids/text plus structuredContent { count, posts } with named fields. Combined with the scope requirement and status semantics, an agent has everything needed to call and consume this tool.

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 coverage is 100%, so the baseline is 3, but the description earns a bump by defining each status value's lifecycle meaning (draft = saved with no time set, ready = time passed and awaiting manual publishing, etc.), which the enum labels alone do not convey. It does not restate the limit parameter, but that is fully documented in the schema.

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 signed-in account's Posts from the library'), plus the default filter, the sort order ('ordered by scheduled_for, soonest first, unscheduled last'), and explicitly claims the role of 'the general Post listing tool' when status is 'all'. That distinguishes it from siblings like list_stories and list_sources without opening any schema.

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 explicit when-to-use guidance: default returns the scheduled queue, pass status 'all' for every Post. It also routes the agent forward by naming the tools that consume the returned ids (schedule_post, cancel_scheduled, export_to_tap), so the next step is unambiguous.

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