create_article

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

Annotations already declare this is a non-read-only, non-destructive write, so the safety profile is covered. The description adds genuinely non-obvious behavior: the backend generates id and slug, posts are auto-filed under a default category, and SEO is deliberately excluded from creation. It omits auth/permission needs and what the response actually returns, keeping it from a 5.

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?

Purpose is front-loaded in the first clause and every sentence carries usable information (surfaces, pipeline, image hosting, category linkage, SEO follow-up). It is dense and slightly long, but nothing reads as filler.

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 5-param write tool with no output schema, the description covers prerequisites and the create-then-update workflow, implying the returned id needed for the SEO step. It does not explicitly state the response shape, which is the only real gap.

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 baseline is 3, but the description adds semantics the schema lacks: title + optional summary framing, the cover-image convention, and the auto-filing side effect of category_ids. It goes beyond restating the JSON schema.

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 precise verb+resource ('Create a blog article') and grounds it in the consuming surfaces (post-list, grid-blog, post-overlay). An agent can distinguish it from update_article, create_blog_category, and other create_* siblings without opening a 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?

Explicitly routes the agent: category_ids come from create_blog_category or list articles' categories, image URLs must be hosted via search_images/upload_images, and SEO must be set afterwards with update_article({ id, seo }). Prerequisites and follow-up steps are all named.

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