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

Annotations already declare a non-read-only, open-world, non-idempotent write, so the description does not need to restate that. It adds real value beyond them by disclosing that the post goes out publicly on the user's behalf and that privacy/other answers are inherited from saved plan settings rather than supplied per call.

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?

Two sentences, front-loaded with the action and effect, with the prerequisite pointer at the end. The phrase 'the privacy and other answers saved in their plan settings' is slightly loose but still earns its place.

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 three-parameter public-publishing mutation with no output schema, the definition covers the action, privacy inheritance, and a prerequisite check. It omits what a successful call returns (e.g., a scheduled post identifier), what happens if only some platforms succeed, and how to recover via retry_post or unschedule_post.

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 clip_id, post_at (including the no-offset timezone rule and omit-to-post-now behavior), and platforms are already documented. The description adds only indirect meaning, clarifying that privacy settings are not a parameter, so baseline 3 is 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 gives a concrete verb and resource ('puts a finished clip on the SnapDub Content Plan') plus the effect ('posted to the person's connected social accounts at a given time (or now)'), which is enough to distinguish it from read-only siblings like get_clip or list_scheduled_posts. It does not explicitly contrast with reschedule_post or unschedule_post, which sit closest to it in the sibling list.

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 points the agent at list_social_accounts to confirm which networks are ready, and the 'at a given time (or now)' phrasing implies the immediate-post case. There is no explicit when-not guidance and no mention of when to use reschedule_post or unschedule_post instead once a post exists.

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