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

There are no annotations, so the description carries the full burden. It gives some context by saying the posts are 'committed to publish,' but it does not disclose whether the operation is read-only, what the output contains, how the days parameter affects results, or any ordering or filtering behavior.

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 description is a single concise sentence with no filler. It is front-loaded with the core resource, though it is phrased as a noun phrase rather than an actionable verb phrase.

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 simple list tool with one optional parameter, the description is minimally viable but leaves gaps: no explicit read-only guarantee, no default behavior, no output shape, and no distinction from related scheduling tools. It is adequate but not 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?

The single optional days parameter has no schema description, and the description's 'coming days' phrase loosely maps to a future-time horizon. This provides partial meaning but does not clearly explain that days controls how far ahead to look or what happens when it is omitted.

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?

The description identifies the resource as posts committed to publish in the coming days, which combines with the tool name to clearly indicate a listing operation. It is not an explicit verb phrase, but it is unambiguous enough to separate from scheduling or canceling tools.

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?

No guidance is given about when to use this tool versus sibling tools like schedule_post, cancel_scheduled_post, or publish_now. The intended context is only implied by the tool name and description.

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