Create a post

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

With no annotations provided, the description carries the transparency burden. It discloses the default status, auto-stamping of published_at, and the two-step draft workflow, plus the required posts:write scope. It doesn't cover error behavior or return value, but the key behavioral traits are well explained.

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 sentences deliver purpose, behavior, alternatives, and prerequisites. Perfectly front-loaded, 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?

Given 9 parameters and no output schema, the description works well with the schema to cover all essential inputs and the publishing workflow. The only gap is not describing what the tool returns (e.g., created post object), which would be helpful without 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 78%, and the schema already details all major parameters. The description adds workflow context (default status, publish_post alternative) that partially reinforces the schema's status description but doesn't add new parameter-specific semantics beyond what's already documented.

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 uses a specific verb ('Creates') and resource ('blog post'), clearly distinguishing this from siblings like update_post, publish_post, or list_posts. It also clarifies the default status and publishing workflow.

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?

Explicitly states when to use publish_post vs. immediate publishing: 'create as a draft and call publish_post once you're ready.' Also names the required scope, giving clear context for when this tool is appropriate.

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