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

The annotations already state that this is a non-destructive, idempotent mutation with no open-world side effects. The description adds the useful constraint that the target must be a scheduled post, but it does not cover failure cases, timezone behavior, or permissions.

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 front-loaded sentence with no filler. The parenthetical uid hint is directly useful and does not distract from the core action.

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 simple two-parameter, idempotent mutation with full schema coverage and clear annotations, the description is largely complete. The remaining gap is minor: it could say more about what happens when the post is no longer scheduled or how time zones are interpreted.

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 parameters are fully documented in the schema, including the ISO 8601 future-datetime format. The description only repeats the post_uid source and adds no further parameter meaning beyond the schema.

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 verb and resource: change the scheduled time of a scheduled post. It also identifies where the uid comes from (list_posts), which helps distinguish it from broader update_post usage, though it does not explicitly name sibling alternatives.

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?

It implies the tool should be used for posts that are still scheduled and points to list_posts for the uid. However, it gives no explicit exclusions such as not using it for published posts or using update_post for other edits.

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