create_draft

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

No annotations are provided, so the description carries the burden of disclosing behavior. It does mention that the draft is saved to Draft Box, but it omits important details such as requirements for thumb_media_id (e.g., being previously uploaded via upload_cover_image) and what the response contains. The disclosure is minimal but not misleading.

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 one concise sentence that is front-loaded with the key action and context. Every word contributes value, with no repetition or filler.

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?

The tool lacks an output schema and the description does not explain return values or the draft's role in the broader workflow (e.g., that it can later be published via publish_draft). The description is adequate for a basic create operation but leaves out useful contextual connections to sibling tools.

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 100% with all six parameters described in the input schema. The description adds no additional parameter-level meaning, so the baseline of 3 applies. It does not clarify relationships between parameters (e.g., thumb_media_id must be from a cover upload), but the schema already defines each parameter's role.

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 clearly specifies the action ('Create'), the resource ('a new article draft'), and the context ('saves to Draft Box'). This distinguishes it from sibling tools like publish_draft and delete_draft, making its purpose unambiguous.

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 'saves to Draft Box' implies the tool is for creating drafts, not publishing, which gives clear usage context. However, it does not explicitly state when not to use it or mention alternatives like publish_draft, though sibling names provide inferable guidance.

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