queue_post

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

Discloses that the payload is finalized at queue time (LLM generation is NOW) and that execution requires process_queue, adding value beyond the annotations which only indicate non-read-only and non-destructive.

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 sentences with the primary action front-loaded and all key details included without redundancy.

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?

Given the moderate complexity and presence of an output schema, the description covers essential behavior but misses details on media and community parameters. Overall, it is fairly complete.

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 description explains the text/topic relationship and not_before as ISO 8601, but does not cover media, account (required), or community parameters. With 0% schema coverage, more parameter explanation is needed.

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 states 'Schedule a post for paced execution' and explains the two modes (verbatim text or LLM-generated topic), distinguishing it from immediate posting tools like post_tweet.

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?

It explains when to use this tool (to schedule a post) and mentions that nothing executes until process_queue is called, but does not explicitly state when not to use it (e.g., for immediate posting).

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