create_article_draft

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one non-obvious side effect: a temporary image URL is automatically uploaded and converted into the permanent cover image. It says nothing about required permissions, whether the draft is immediately published or private, what happens on slug collision, or whether fields are validated.

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 tight sentences, front-loaded with the core action and then the image-upload tip. No filler or repetition, though the brevity is partly under-specification rather than deliberate economy.

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?

With 16 parameters, 0% schema coverage, no annotations, and no output schema, the description is far too thin for the tool's complexity. An agent cannot confidently populate most optional fields or predict the return value from this definition alone.

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% across 16 parameters, so the description is the only source of parameter meaning — and it explains just one of them (temporaryCoverImageUrl). It never clarifies the relationship or difference between coverImage and temporaryCoverImageUrl, nor what linkPolicy, imagePrompt, categoryId, authorRole, or canonicalUrl do.

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 and resource ('Create a completed article draft'), so the agent knows this is a creation/authoring tool. It does not distinguish itself from the sibling update_article_draft or explain why one would create a draft here versus elsewhere, so it stops short of the top score.

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 gives one concrete usage instruction — pass a temporary image URL here to have it uploaded and attached — which is genuinely useful routing for that parameter. However, it offers no guidance on when to use create_article_draft versus update_article_draft, no prerequisites (e.g. needing a siteSlug from list_publications), and no mention of what happens on an existing slug.

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