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

Annotations already cover readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds modest context by emphasizing 'new' and mentioning publishing options, which implies side effects and status choices, but it does not disclose specifics such as permissions for author assignment or the default draft behavior beyond the schema.

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?

A single efficient sentence front-loads the core action ('Create a new blog post') and then concisely lists the relevant aspects. No filler or repetitive prose.

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 a complete input schema, an output schema, and annotations covering safety/idempotency, the description is mostly sufficient for an agent to invoke this tool correctly. A small gap is the absence of a pointer to alternative creation tools, but that is more of a usage-guidance issue than a completeness issue for this resource.

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 schema already documents every parameter's meaning and constraints. The description's field list adds no new semantic detail beyond restating the parameter names.

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 opens with a specific verb and resource: 'Create a new blog post', and enumerates the involved fields (title, HTML content, author, collection, tags, metadata, slug, image, publishing options). This clearly distinguishes it from sibling tools like create_page and create_collection.

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 no explicit when-to-use or when-not-to-use guidance and names no alternatives. The agent must infer from the name and schema that this is for posts, not pages, collections, or redirects.

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