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

Adds real context beyond the annotations: the >1 minute lead-time constraint, the required ISO-with-offset format, and the irreversibility implied by 'goes live at that time without further confirmation' — which substantiates the destructive/openWorld hints. It doesn't cover failure modes, reschedule behavior, or whether an already-scheduled post can be changed.

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?

Four dense sentences, bracketed tag first, core action and timing constraint front-loaded, then parameter formats, then the consequence. No filler.

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 5-parameter mutation with no output schema and zero schema coverage, the definition covers every parameter and the main behavioral consequence. Minor gaps remain around what happens on failure or if the draft is not in an approved state.

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%, so the description carries the full burden and does it: it documents the datetime format and lead-time rule, the platform enum (ig|fb|tw|tt|yt|li|th|tg — absent from the schema), the post_id shape (<platform>_post_id), and post_uuid as the alternate identifier, plus that caption is optional.

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?

States a specific verb (schedule), resource (one approved draft social post), and the exact effect: sets publish time plus optional caption. The word 'Schedule' plus 'approved draft' separates it from create_social_post and publish_social_post without needing to name them.

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?

Makes the precondition clear ('one approved draft') and warns that the post goes live at that time with no further confirmation, which is the key usage context. It stops short of naming the alternatives (e.g. publishing immediately vs scheduling) or stating when not to use it.

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