reschedule_post

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

No annotations are provided, so the description must fully convey behavioral traits. It states the tool moves a scheduled post, implying mutation, but does not disclose what happens if the post is not in a scheduled state, whether it requires specific permissions, or what the return value is. The description is too brief to provide adequate 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 consists of two terse sentences, front-loading the core purpose ('move a scheduled post to a new time') and immediately providing clarifying equivalence. Every word earns its place with no waste.

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 low complexity (2 params, no output schema, no annotations), the description covers the essential action but lacks details on return values or side effects. It is minimally adequate but not comprehensive for an agent to fully understand consequences.

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 input schema covers both parameters with clear descriptions ('id' and 'scheduled_at'), achieving 100% coverage. The description adds no additional meaning beyond the schema, earning the baseline score of 3.

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 verb 'move' and resource 'scheduled post' with a specific purpose: rescheduling to a new time. It explicitly distinguishes itself from 'update_post' by noting equivalence with only 'scheduled_at' set, which differentiates it from the more general update tool.

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 frames the tool as a 'Shortcut' implying convenience, and mentions equivalence to update_post, suggesting it is a specialized alternative. However, it does not explicitly state when to use this tool over siblings like 'schedule_post' or 'publish_now', nor does it provide exclusions.

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