Edit scheduled post

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

Annotations already indicate destructiveHint=true, so the description's mention of 'Reschedule' aligns. However, the description adds no additional behavioral context beyond the annotations, such as whether the operation requires specific permissions or what happens to the original scheduling. It meets the baseline but adds little extra insight.

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 a single, well-structured sentence that front-loads the core action ('Reschedule a post'). It contains no superfluous words and is immediately informative.

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?

Despite the presence of an output schema, the description omits critical details such as the expected format for scheduledDate (e.g., ISO 8601) and timezone (e.g., IANA timezone). For a tool with three parameters, this brevity leaves the agent uncertain about how to correctly invoke it.

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%, so the description must compensate fully. It adds meaning for two parameters (scheduledDate and timezone) by stating 'change date and/or timezone', but it does not explain the required jobId parameter. The format or constraints for date and timezone are also missing, leaving gaps for the agent.

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 the tool's purpose: 'Reschedule a post: change date and/or timezone.' It uses a specific verb-resource combination ('Reschedule a post') and specifies the mutable fields, distinguishing it from sibling tools like cancel_scheduled (which cancels rather than edits).

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 provides no guidance on when to use this tool versus alternatives (e.g., cancel_scheduled). It does not mention prerequisites, exclusions, or scenarios where using this tool is not appropriate. Only the basic action is stated.

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