create_blog_post_from_markdown

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

With no annotations, the description carries the full burden and does well: it discloses the always-draft status, that agents cannot publish, that Studio review is required, and that a specific CLI performs the conversion. It omits auth/permission needs and what happens on a duplicate slug or conversion failure, but the critical behavioral constraint is surfaced.

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?

Three tightly written sentences with the primary action front-loaded and the draft constraint immediately after. No filler; each sentence contributes a distinct fact.

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 12-parameter mutation tool with no annotations and no output schema, the description covers the essential behavioral constraint and the conversion mechanism. The notable gap is that it never says what is returned (e.g. the new post id), which matters more given the absence of an output schema.

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 all 12 parameters are already documented in the schema. The description only restates two of them (markdown_body conversion, category_slug linking), adding no syntax, format, or default details beyond what the schema provides. Baseline 3 is appropriate.

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 chain (convert Markdown → PlateJS JSON) and a specific resource (draft blog post), which cleanly distinguishes it from update_blog_post and create_content. An agent can tell what this does without opening the schema.

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?

Clearly conveys the usage context: use it to insert a Markdown body as a draft, with category linking by slug. The draft-only constraint is spelled out, but it never names a sibling (e.g. update_blog_post for edits, create_content for non-blog content) to route the agent between alternatives.

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