create_draft

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning the tool is a write operation. The description adds behavioral context: it accepts markdown and converts it, and it does not publish. This goes beyond the annotations, providing useful details about the tool's behavior.

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 two sentences, front-loaded with the primary action, and includes both the core function and a key constraint. Every sentence adds value with no wasted words.

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 has 4 parameters and no output schema. The description covers the main behavior (creating a draft with markdown conversion) and the non-publishing aspect. It does not detail return values or prerequisites, but for a straightforward creation tool, the description is sufficiently complete.

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 the baseline is 3. The description adds context for the 'body' parameter by stating 'Accepts markdown body which is converted to Substack's format', which clarifies the expected input format beyond the schema's description. This extra information warrants a score of 4.

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 states the action ('Create a new draft post'), the resource ('draft post'), and distinguishes from publishing ('Does NOT publish'). The verb 'create' and resource 'draft post' are specific, and the description differentiates from siblings like 'update_draft' or 'get_draft'.

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 description explicitly states 'Does NOT publish — creates a draft only', which helps the agent understand when to use this tool versus a publishing tool. It provides clear context but does not explicitly mention when not to use it or name specific alternatives beyond the implication.

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