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

Annotations only declare openWorldHint=true, so the description must carry the rest. It usefully discloses the deferred, time-triggered nature of publishing and the target accounts, but says nothing about permissions, failure handling, whether the schedule can be modified or cancelled, or how the job is dispatched.

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?

A single front-loaded sentence with the verb and resource first and no filler. Every clause (finished, connected accounts, future UTC time) contributes information.

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 and 4 parameters, the description covers the core action but omits the optional privacy parameter and any statement about what happens after scheduling succeeds or fails. Adequate but with noticeable gaps.

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 50%, and the description restates the platform set and the UTC-time requirement already present in the schema, adding little new syntax or format detail. It never explains job_id or the youtube_privacy_status parameter, leaving those gaps unaddressed.

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 (a finished reel), and destination (TikTok/Instagram/YouTube Shorts) plus the trigger (future UTC time). This clearly separates it from create_reel (creates content) and list_scheduled (reads scheduled items).

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 phrase 'finished reel' implies the prerequisite that the job must already be complete, and 'connected accounts' hints at the setup requirement, but no explicit when-to-use guidance, exclusions, or pointer to list_scheduled for verifying/cancelling schedules is given.

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