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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's added sentence, that this 'creates an externally visible post', supplies the concrete real-world consequence the annotation cannot convey. It stops short of covering permission requirements, irreversibility of an already-published post, or how idempotencyKey affects retries.

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 short sentences, purpose first and consequence second, with no filler. Nothing could be removed without losing 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 an externally visible, irreversible-feeling mutation with four undocumented parameters and no output schema, the description is serviceable but thin. It never explains the idempotency contract or what a successful publish returns, which an agent needs before firing this call.

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 0%, so the description must carry parameter meaning, and it largely does not. 'Schedule' weakly implies scheduledFor and 'generated clip' weakly implies clipId, but idempotencyKey and connectionId are entirely unaddressed despite being required/meaningful inputs.

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 concrete verb pair (publish/schedule), the resource (a generated clip), and the target (a connected social account), which is enough to separate it from publish_content. It does not name a sibling explicitly, but the 'clip' vs 'content' distinction is inherent in the wording.

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?

There is no guidance on when to choose this over publish_content or retry_clip_publish, no mention that a connectionId must first be obtained (e.g. from list_publish_destinations), and no statement about immediate vs scheduled publishing rules.

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