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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: creation always lands as a draft unless a flag is set, and timestamps must carry an ISO-8601 offset. The 'not idempotent' sentence merely restates the idempotentHint annotation.

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 short sentences, front-loaded with the default behavior and the two mutually exclusive publication paths. No filler; the ISO-8601 constraint is placed where it is needed.

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 an output schema present, return values need no explanation, and the rich 9-parameter schema carries the field-level detail. The remaining gap is guidance on how this tool relates to its publish_post/schedule_post/validate_post siblings, which matters given the overlapping capabilities.

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%, so the baseline is 3. The description usefully clarifies the interplay between scheduled_at and publish_now relative to the draft default, but it largely restates what the per-parameter schema text already documents.

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?

Clear verb+resource ('Creates a post') with a stated default behavior (saved as draft). However, it never addresses the obvious overlap with sibling tools publish_post and schedule_post, which appear to do what publish_now and scheduled_at do here, leaving an agent unsure which tool to pick.

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 implies usage through the flag semantics (default draft, scheduled_at to schedule, publish_now to publish), but never states when to call this versus publish_post, schedule_post, or validate_post. No prerequisites beyond the schema-level 'requires workspace opt-in' are surfaced in the description.

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