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

Annotations already declare non-readOnly, non-idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the meaningful fact that scheduling operates on a draft with a future timestamp, but says nothing about failure modes an agent would care about (past timestamps, duplicate scheduling given idempotentHint=false, or whether the post publishes immediately if the time has passed).

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, zero filler, with the primary action front-loaded and the input-mode caveat second. Every clause carries 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 no output schema, the description leaves the agent guessing what a successful schedule returns (an ID? a confirmation?), and it does not address the notable schema gap that 'platform' is optional despite being described as the target platform. For a 6-parameter mutation with only one required field, more guidance on which combinations are valid would be warranted.

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 baseline is 3, but the description adds meaning the schema does not encode: that 'content' and 'content_id' are alternative input paths for the same underlying object rather than independent fields. It also frames scheduled_for as a future publish target, reinforcing the ISO 8601 schema note.

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+resource ('Schedule a draft post for publishing') plus the temporal scope ('designated future time'), which cleanly separates it from siblings like generate_post and cancel_scheduled. It stops short of naming any sibling explicitly, so the differentiation is inferential 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?

The sentence 'Supply content directly or reference existing content_id' gives genuine mode-selection guidance for the two input paths, but there is no guidance on when to prefer this over generate_post or how it relates to cancel_scheduled/list_scheduled. Usage is implied rather than stated.

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