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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses that the draft is private, not public until publish/schedule, requires the user's Cotlet API key or sign-in, and needs no confirmation. This is useful behavioral context, though the phrasing about being 'deleted or edited in one call' is somewhat unclear.

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 front-loaded and understandable, but it repeats itself: 'New draft from Markdown' and 'Creates a draft from Markdown,' plus 'Nothing is public' and 'The draft is private.' Several sentences restate the same idea rather than adding new 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 a six-parameter creation tool with no output schema, the description covers the essential context: it is private, needs authentication, returns a story_id, and does not publish automatically. It is largely complete, though it could clarify edit/delete behavior more precisely.

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%, so the parameters are already fully documented by the input schema. The description adds only that the draft is built 'from Markdown' and returns a story_id, which does not add meaningful semantics beyond the structured fields.

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 names the specific action and resource: 'Creates a draft from Markdown and returns its story_id.' It also distinguishes the draft state from publishing/scheduling, so an agent can tell it apart from siblings like medium_publish_story or medium_schedule_story.

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 clear context for when to use this tool: creating a private draft before it is published or scheduled. It does not explicitly name alternative tools such as update_story or publish_story as alternatives, but the usage boundary is clear.

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