publish_article

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

Discloses many behaviors: validation orchestration, slug generation (transliteration + date + collision counter), cover image selection logic, IndexNow fire-and-forget, and contentFile alternative. With no annotations, description carries full burden and does well, though missing potential constraints like rate limits.

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?

Concise paragraph with bullet-like structure using emoji and line breaks. Front-loaded with the main action. Slightly dense but every sentence adds value.

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?

Covers all major aspects: validation, title/content relationship, slug generation, cover image, IndexNow, large content. No output schema, but description explains how to get the slug from response. Adequate for the tool's complexity.

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?

Adds meaning beyond schema for title (optional if content starts with heading), content (Markdown), contentFile (path to .md), skipValidation (bypass errors). 'site' and 'tags' are not elaborated but schema covers tags. Baseline 3 for 50% coverage, description earns extra point.

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 clearly states the verb 'Опубликовать' (publish) and resource 'НОВУЮ статью' (new article), and includes the HTTP method POST. It distinguishes from siblings like update_article and delete_article.

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?

Provides explicit guidance on running validate_article first, handling errors and warnings, title and content alternatives, slug generation, cover image logic, and IndexNow. Does not explicitly state when not to use it, but context is clear.

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