Publishing limit

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the window is rolling 24 hours, it reflects Meta's platform limit, and carousels count as a single post — counting rules an agent could not infer otherwise. It stops short of describing the response fields or what happens when the count reaches zero.

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?

One sentence, front-loaded with the primary answer (remaining posts) and the secondary one (scheduled posts). The parenthetical about carousels earns its place; there is no filler.

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?

With one optional parameter, no output schema, and annotations covering safety, the description is nearly complete — it explains the units and rules of the count. A small gap is the lack of any pointer to how the returned numbers map to publish decisions or to the sibling used for editing the schedule.

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% for the single optional 'account' parameter, including the default-account behavior, so the schema does the work. The description adds nothing about account scoping, which is the baseline-3 outcome.

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 states precisely what the tool returns: remaining API posts in Instagram's rolling 24-hour window plus posts scheduled for the next 24 hours. That is specific enough to separate it from siblings like list_scheduled or get_publish_status, though it never names those alternatives to reinforce the distinction.

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?

Usage is only implied — an agent can infer it is a pre-publish quota check, but the description never says when to call it or when another sibling (e.g. list_scheduled for full schedules, get_publish_status for a specific post) would be the better choice. No exclusions or prerequisites are stated.

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