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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety characteristics are covered. The description adds a useful behavioral caution about confirming the time with a person, but it does not disclose timezone handling, what happens to past times, or whether the post can be cancelled afterward.

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?

Two short sentences with no wasted words. The primary action is front-loaded, and the confirmation caution follows immediately.

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 scheduling mutation with no output schema, the description gives the essential source for variant_id and a time-confirmation requirement. It is incomplete on timezone semantics and does not explain the expected outcome of scheduling, such as whether the post becomes visible in list_scheduled_posts.

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?

With only 33% schema description coverage, the description partially compensates by explaining that variant_id comes from compose_post or the plan. However, it does not clarify the timezone parameter or how scheduled_at and timezone interact, leaving a significant gap.

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 uses a specific verb and resource: 'Schedule a draft post ... to publish at a given time.' It also identifies variant_id as coming from compose_post or the plan, but it does not explicitly distinguish this tool from siblings such as publish_now or cancel_scheduled_post.

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 gives clear context for when to use the tool: scheduling a draft post for future publication, after compose_post or a plan. It also adds an operational caution, 'Confirm the time with the person first,' but does not state when not to use it or name alternative tools like publish_now.

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