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

Annotations declare idempotent=true, destructive=false, readOnly=false, so the safety profile is partly covered. The description adds meaningful behavior beyond that: the time is placed on the draft card, the person (not the AI) actually publishes/schedules in Studio, and consent is required via the 'groups' policy. This clarifies the surprising fact that the write does not itself publish, which annotations alone would not convey.

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?

The core purpose is front-loaded, but the prose is convoluted with em-dashes and parenthetical asides ('even when this AI may otherwise send directly'), making it harder to parse than necessary. The content is mostly worthwhile, but the structure is denser and less scannable than ideal.

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 not be explained. The description covers the purpose, the valid time range, the consent requirement, and the key behavioral constraint that publication is done by the person. It is fairly complete for a two-parameter scheduling tool, though the when-to-use framing remains implicit.

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. The description adds genuine meaning beyond the schema by stating the allowed range (5 minutes to 30 days ahead) for the 'at' time, which the schema does not express. The draftId is only referenced implicitly through 'post draft (from create_post_draft)'.

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 states a specific action and resource: recording WHEN a draft (from create_post_draft) should go out, with the 5-minute to 30-day window. It references the sibling create_post_draft, so an agent can tell it apart from drafting vs. scheduling. The phrasing 'Note WHEN... to go out' is slightly indirect but conveys the purpose.

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 some usage conditions: only with the person's go-ahead on the time, and the 'groups' policy ('off' refuses) gates the action. However, it never explicitly says when to use this versus alternatives or states prerequisites in a clean when-to-use form; the guidance is implied and buried in dense prose.

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