Write and schedule a post

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

Goes well beyond the annotations by disclosing the free-plan rate limit (10 posts/day), the 402 free_daily_cap reset behavior, the required 'publish' scope, and that the post lands in the account's next free queue slot. These are operationally critical facts the schema and annotations do not carry.

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?

Dense and front-loaded with the core action first, then preconditions, then limits. The telegraphic style is efficient, though a few clauses ('at a time, in the account's next free queue slot, or now') are slightly compressed.

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?

An output schema exists and annotations cover safety, so return format is not needed. The description supplies the missing prerequisites and rate-limit context; only the routing versus posts_publish/posts_approve is left unaddressed.

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 100% and the field descriptions are already rich, so the baseline is 3. The description mostly restates schema content (queue vs scheduledAt, settings via platforms_list) and adds only cross-tool references rather than new parameter semantics.

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?

Opens with a specific verb+resource ('PUBLISHES CONTENT: puts a post you wrote on the rail') and names scope ('one connected account'). It is clear what it does, but it never differentiates itself from the sibling 'posts_publish' (or 'posts_approve'), which an agent must disambiguate against.

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?

Gives real preconditions: read platforms_list first for limits/settings schema, needs the publish scope, and describes the queue-vs-now-vs-scheduledAt selection. Lacks any explicit exclusion or contrast against sibling publishing tools.

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