Move a scheduled post

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true); the description goes well beyond them by disclosing atomic group semantics (three rows sharing one time must move together), a hard refusal mode on partial input, and a minimum-lead-time constraint on the new timestamp. These are failure conditions an agent cannot infer from structured data.

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 sentences, front-loaded with the purpose, then the critical constraint, then the state and timing limits. No filler, and dropping any sentence would lose a rule the caller needs.

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 no output schema, the description could say more about what comes back on success (e.g., updated post state or confirmation), but it fully covers preconditions, atomicity, and refusal behavior for a mutation tool. Nothing critical for correct invocation is missing.

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 100%, so the baseline is 3. The description still adds value by explaining why postIds is a group (one post spanning three accounts is three rows) and by reinforcing the ~5-minute lead time already hinted at in the schema description.

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?

States a specific verb and resource ('Change when a scheduled post publishes'), which clearly separates it from siblings like cancel_posts, list_posts, and schedule_rush_lineup. An agent can identify the operation without opening the schema.

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?

Gives explicit preconditions ('Only works while the posts are still scheduled', 'the new time must be a few minutes out') and the exact invocation rule ('Pass EVERY id in the group'), with the consequence spelled out ('a partial list is refused'). It also points at list_posts as the source of ids, effectively routing the agent to the right sibling.

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