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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety/write profile is covered. The description adds one useful precondition (only SCHEDULED posts, only the future publish time changes), but omits error behavior for non-scheduled posts and does not clarify whether the prior time is replaced or retained.

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 front-loaded sentence with zero filler; the scope qualifier 'SCHEDULED' appears before the action. It is efficient, though arguably too terse for a mutation tool, which is penalized under other dimensions rather than here.

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 mutation with full annotation coverage and a fully documented three-param schema, the description covers the core scope but leaves gaps: no error/precondition handling for non-scheduled posts, no note on whether rescheduling supersedes the previous time, and no mention of approval or publishing side effects.

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% (three params fully documented, including the ISO 8601 future-datetime constraint and IANA timezone), so the baseline is 3. The description only reinforces 'future' via 'future publish time' and adds no format or validation detail 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?

States a specific verb ('Changes') and resource ('publish time') scoped to a 'SCHEDULED post,' which reasonably separates it from siblings like invoke_schedule_post and invoke_cancel_scheduled_post. It does not name any sibling explicitly, so differentiation is inferred rather than stated.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The capitalized 'SCHEDULED' implies a precondition (post must already be scheduled) but the description never tells the agent what to do if the post is a draft, already published, or being approved instead.

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