create_draft

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

With no annotations, the description carries full burden. It discloses that the draft lands in 'pending' status, does not auto-publish, requires publicly accessible media URLs, and notes that uploading from chat is not supported. It also mentions the Review queue, giving useful side-effect context.

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 well-structured: a clear opening statement, then flow of how the draft is created and what happens after. Each sentence contributes meaningful information without redundancy.

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?

While the description is comprehensive about creation behavior and post-creation workflow, it does not explicitly state the return value/shape of the created draft. In the absence of an output schema, this would be helpful for agents to handle the response.

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?

The description adds critical context beyond the schema: it lists required parameters, explains contentType semantics, and constrains mediaItems to publicly accessible URLs. The 'uploading not supported' nuance is not present in the schema and is essential for correct invocation.

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 starts with 'Create a new draft post in the user's Vibe Marketing workspace,' clearly stating the verb and resource. It also distinguishes this tool from siblings by noting that the draft does NOT publish automatically, contrasting with publish/approve tools.

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 explicitly says 'Use this whenever the user wants to draft a social post.' It also references approve_and_publish_now / approve_and_schedule as the next steps, providing alternative tools and clarifying when this tool is appropriate.

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