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

Annotations already declare this is non-read-only, non-idempotent, open-world, and destructive. Beyond that, the description adds valuable behavior: timezone interpretation, skipped networks being listed, and allowance consumption one per network. It does not, however, explain idempotency or what happens on repeated scheduling beyond what annotations imply.

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 description is front-loaded with the core action and then enumerates scheduling modes tightly. Every sentence carries useful operational detail, with no filler or repetitive restatement of the title.

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 scheduling mutation with no output schema, the description covers the key operational facts: timezone handling, skipped networks, and allowance impact. It is nearly complete, though it could clarify how this differs from reschedule_post and whether repeated calls alter an existing schedule.

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 the schema already documents the parameters. The description still adds meaningful semantics beyond the schema by explaining 'best' timing, use_queue behavior, timezone interpretation, and per-network scheduling, though it does not detail every parameter interaction.

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 verb and resource: 'Schedules a saved post.' It is clear what the tool does, but it does not explicitly differentiate it from siblings like reschedule_post or publish_post_now, leaving sibling selection 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?

The description explains scheduling modes (single time, per-network times, 'best', or use_queue), which is useful usage context. However, it gives no explicit guidance on when to choose this tool over reschedule_post, publish_post_now, or pause_post, so alternative selection remains implied.

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