metricool_get_scheduled_posts

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

No annotations are provided, so the description carries the full behavioral burden, and it does little: it does not say whether results are paginated, sorted, or bounded, which matters for a claim of returning 'all' posts. The only added context is that the queue contains pending posts, which is a small clue about return contents but not about retrieval behavior, auth, or limits.

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?

Two short sentences, zero filler, with the core action front-loaded and the clarifying content detail immediately after.

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 one-parameter read tool with no output schema and no annotations, the description is close to sufficient. The remaining gap is operational detail (pagination or limits on 'all' posts) rather than anything an agent needs to form the call.

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% and there is a single required parameter, so the schema already documents brandId. The phrase 'for a brand' reinforces that meaning but adds no format, source, or example detail beyond 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 ('Get all scheduled posts for a brand') and clarifies the content as 'pending posts in the queue.' It is distinguishable from metricool_schedule_post (a write) without opening the schema, but it never explicitly contrasts itself with any sibling.

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?

There is no statement of when to use this tool versus metricool_get_analytics, metricool_get_best_time, or metricool_get_brands, nor any prerequisite guidance (e.g., call get_brands first to obtain brandId). Usage is only implied by the tool name.

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