Get Scheduled Posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the 'scheduled (unpublished)' context but does not disclose pagination behavior, rate limits, or response format details beyond the implicit parameters.

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 concise with one clear sentence and bulleted args, but it could be more efficient by including all parameters and still remaining brief.

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 listing tool with 4 parameters and no output schema, the description is somewhat incomplete, missing pagination and response format details, but it provides adequate basics for typical use.

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 low (25%), and the description adds value for page_id and limit via brief explanations, but it omits the 'after' and 'response_format' parameters, leaving them fully undocumented.

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 clearly defines the tool's action as listing scheduled (unpublished) posts for a Facebook Page, using specific verbs and resource identification that distinguishes it from sibling tools like meta_get_published_posts.

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 implies usage for scheduled posts but lacks explicit guidance on when to use this over alternatives like meta_get_posts or meta_get_promotable_posts, and provides no exclusion criteria.

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