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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so safety profile is covered. The description adds the useful invariant that content is untouched, but never explains that rescheduling overwrites the prior scheduled time or that it fails for sent publications — the latter only appears incidentally in the pinAfterPublish parameter text.

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?

Three short sentences, front-loaded with the trigger condition, then the required inputs, then the key scope invariant. No filler and nothing that could be trimmed without losing information.

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?

With full schema coverage, an output schema, and rich annotations, the description only needs to frame intent and scope, which it does. The one gap is behavior for out-of-range or invalid target times (e.g., a date in the past) on a destructive, idempotent mutation.

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 100%, so both required parameters are fully documented with format examples and a timezone-resolution instruction. The description restates publicationId and the ISO-with-offset requirement without adding new detail, and it omits the optional pinAfterPublish parameter entirely, leaving it at the baseline.

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 precise action (change the date/time) on a precise resource (one pending publication) and adds a negative scope note ('Does not change its content') that separates it from content-editing tools like update_post. It does not explicitly contrast with schedule_post, cancel_publication, or delete_publication, so sibling differentiation is only partial.

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?

'Use when the author asks to change the date or time of one pending publication' gives a clear trigger condition and restricts the tool to a single pending item. It stops short of naming alternatives or stating when not to use it (e.g., for already-sent publications, or for bulk rescheduling).

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