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

Annotations declare destructive=true and openWorld=true, and the description goes well beyond them: publication is irreversible and publicly visible, confirmation must be explicit, and rejection behavior for stale times is spelled out. It also anchors time computation to server now (retrieved_at), which is genuinely non-obvious operational context.

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?

Purpose is front-loaded in the first sentence, then each subsequent sentence adds a distinct rule (staggering, irreversibility, confirmation, time arithmetic, rejection). No sentence merely restates the name, title, or annotations.

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 destructive, open-world mutation with an output schema, the description covers the risky parts: confirmation, irreversibility, and timestamp computation. It leaves open whether platform_schedules replaces or merges with existing entries and what happens if some platforms fail while others publish.

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?

Top-level coverage is 0%, but the description compensates with semantics the nested schema does not state: scheduled_at is UTC, ≥10 minutes ahead, measured from server now, and computed post-confirmation. It adds nothing about natural_posting or timezone, though those properties are already richly documented inline in 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?

Specific verb+resource+precondition: "Schedule a DRAFT post for automatic publication," which implicitly rules out non-DRAFT posts and distinguishes it from publish_draft. It never names sibling tools such as update_schedule or unschedule_post, so the create-vs-modify boundary is left to inference.

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 strong operative rules: scheduling requires the user's explicit confirmation, the timestamp must be computed after that confirmation, relative phrasings need a 15-minute margin, and a past time is rejected rather than moved. It stops short of routing the agent to alternatives (update_schedule for an existing schedule, unschedule_post to cancel), which is the main missing piece.

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