Send due scheduled posts (requires confirm)

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, but say nothing about the two-mode behavior. The description adds the critical fact that omitting confirm yields a preview rather than a send, which is real value beyond the structured data. It omits idempotency/re-run behavior and failure handling, keeping it from a 5.

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 action, then the mode switch, then the intended caller. No filler and nothing redundant.

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 and sparse annotations, the description covers the operation, its two modes, and its intended trigger. It leaves out return shape for the preview mode and re-run/idempotency semantics, which are relevant for a cron-driven sender.

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 0% and the confirm boolean has no schema description, so the description must carry the meaning — and it does, fully specifying that confirm:true sends while its absence previews. Only the parameter's exact naming/typing detail is left to 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 with a scoping qualifier ('scheduled posts whose time has come') that separates it from post_message, schedule_post, and list_scheduled_posts. An agent can identify the exact operation 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?

Gives clear context for when to use it ('Intended for a cron job the user set up') and explains the dry-run vs live distinction. It does not name sibling alternatives or state when NOT to use it, so it falls short of a 5.

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