schedule_post

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

No annotations are provided, so the description carries the full burden. It discloses that the post is published by the scheduler process and requires the scheduler to be running, adding key behavioral context beyond the schema. It also provides format examples for the 'when' parameter, enhancing transparency.

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 compact and front-loaded, with the core purpose stated first, followed by necessary time-format examples and a critical operational note. Every sentence earns its place 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?

For a scheduling tool with no output schema and no annotations, the description covers the essential aspects: what the tool does, how the timing works, and the necessary prerequisite (scheduler). It could mention error handling or edge cases, but it is sufficiently complete for an AI agent to invoke it correctly.

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 0%, and the description compensates well for the 'when' parameter by explaining both ISO and relative time formats. However, it offers no additional meaning for 'text' or 'visibility', leaving a gap in parameter understanding, though these are relatively self-explanatory.

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 opens with 'Queue a post for later', using a specific verb and resource, and immediately distinguishes from the sibling 'publish_now'. It clearly states the tool's purpose as scheduling a post for future publication.

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 explains the context of use (delayed publishing) and gives an explicit operational instruction: run the scheduler for queued posts to be published. It doesn't explicitly name alternatives, but the sibling 'publish_now' provides the contrast, making the usage context clear.

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