create_post

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

With no annotations, the description carries the full burden. It usefully discloses a behavioral trait the schema does not (the draft default, since the 'draft' property has no schema description or default), but says nothing about permissions, what publishing does, validation limits, or error 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?

Two short, front-loaded sentences with no wasted words. The phrasing 'Defaults to draft unless draft=false' is a slightly awkward double negative, but it is efficient and readable.

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 an 8-parameter mutation tool with no annotations and no output schema, this is thin. Nothing is said about what the created post looks like on return, what happens on validation failure, how the permalink is derived, or what permissions are required.

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 only 25% (body and date described), and the description only adds meaning for one parameter, 'draft'. Six of eight parameters — title, tags, subtitle, permalink, read_time, date — receive no clarifying semantics beyond their bare JSON-Schema types.

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 and resource: 'Create a blog post.' An agent can identify the operation immediately. It does not, however, differentiate itself from the closely named siblings create_page/update_post, so it stops short of 5.

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 draft-default note gives an implied workflow hint (create posts unpublished unless overridden), but there is no explicit when-to-use guidance versus update_post or create_page, and no stated prerequisites or publish path.

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