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

Annotations already mark it as a mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that the new date must be in the future, which is useful, but it does not disclose side effects such as cancellation of the old schedule, validation rules, or idempotency.

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?

A single sentence with no filler; the core operation and constraint ('future') are front-loaded. Every word earns its place.

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 two-parameter mutation with no output schema and no enum documentation, the description is too thin to allow reliable invocation: an agent still lacks the scheduledFor format and any behavior around the original schedule. The low parameter coverage and absent usage guidance make this incomplete despite the simple surface.

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 0% and both parameters are bare strings, so the description must carry the semantics. It implies id is the existing post and scheduledFor is the new future date, but it does not specify the expected date format, timezone, or whether id is a post ID rather than a scheduling entry ID.

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 states a specific action ('Move an existing post') with a clear target state ('a new future publication date'), so an agent can tell this reschedules rather than creates or deletes. It does not explicitly contrast with update_post, which may also edit scheduling fields, so it loses a point on sibling differentiation.

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 gives no guidance on when to choose reschedule_post over update_post or the other post-management siblings. There is no mention of prerequisites, constraints, or when not to use this tool.

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