list_scheduled_posts

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

With no annotations, the description carries the behavioral disclosure burden. It clarifies that the tool lists current statuses and enumerates possible values, which is useful, but it does not disclose whether the operation is read-only, whether results are ordered, or what the actual return shape looks like.

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 efficient sentence that names the resource and the key status values without filler. Every word contributes to agent understanding, and the status list is front-loaded after the primary purpose.

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 zero-parameter list tool with no output schema, the description conveys the essential behavior and expected status output. It is slightly incomplete because it does not describe the result format or any ordering/filtering behavior, but these are minor given the tool's simplicity.

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 input schema has zero parameters, so the baseline is 4 because there is no parameter meaning to document. The description appropriately focuses on what the tool returns rather than parameters, and no parameter information is missing.

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 uses a specific verb ('List') and a resource ('scheduled reels') with an explicit status enumeration. It is distinguishable from siblings like schedule_reel and cancel_scheduled_post, though the slight mismatch between the tool name 'scheduled_posts' and description 'scheduled reels' introduces minor ambiguity.

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 description makes its scope clear by listing all scheduled reels and statuses, which implies when an agent would use it. However, it provides no explicit guidance about when to choose this tool over alternatives such as list_media or cancel_scheduled_post, and no exclusions are stated.

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