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

Annotations declare destructiveHint=true and openWorldHint=true; the description adds real behavioral context beyond that — the first call posts nothing, it returns a preview and token, and the token must be replayed with identical arguments. It does not explain why the operation is flagged destructive, whether a scheduled post can be cancelled or edited afterward, or any rate limits, so it stops short of full disclosure.

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 tight sentences: purpose first, then the two-call protocol, then the time constraint. Every sentence carries an actionable constraint and there is no filler or repetition.

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 no output schema and 7 parameters, the description covers the critical flow (preview-then-confirm) and the timing rule, which is what an agent most needs. It omits post-scheduling lifecycle details (cancellation, editing, failure behavior), leaving a modest gap.

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 every parameter is already documented in the schema, including the UTC/ten-minutes and confirmation_token semantics. The description restates those constraints in prose but adds no syntax, format, or edge-case meaning the schema lacks, making the baseline 3 appropriate.

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 precise verb and resource ('Add a post to the user's scheduled queue') and adds the defining scope ('publish unattended at a time they choose'), which separates it in intent from the immediate-publish sibling publish_post. An agent can identify what the tool does without opening the schema.

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 an explicit two-phase invocation protocol: call once without confirmation_token for a preview and token, then again with the token only after user agreement. That is clear operational guidance, but it never names the alternative tool (publish_post for immediate posting) or states when scheduling is the wrong choice, so it falls short of 5.

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