generate_blog_post

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

With no annotations, the description carries the full burden and discloses key behaviors: async generation requiring polling, return of articleId and operationId, and the exact follow-up calls. It doesn't mention failure modes or side effects like credit consumption, but the critical async behavior is well covered.

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?

Every sentence is packed with actionable information: prerequisites, async behavior, follow-up tools, and publication steps. No fluff or repetition; it's concise and clearly structured.

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?

The description covers the full lifecycle for a complex async tool: prerequisites, input sources, output identifiers, polling, retrieval, editing, and publishing. It's complete enough even without an output schema, and the sibling references orient the agent within the broader toolset.

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 92%, so the baseline is 3. The description adds meaningful value beyond the schema by explaining the provenance of publicationId and voiceProfileId, and reinforcing the async flow. It doesn't just restate parameter descriptions.

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 'Generate a full AI blog article,' using a specific verb and resource. It clearly distinguishes itself from sibling tools like generate_post (social posts) and generate_text by focusing on blog articles with a publicationId requirement.

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 clear context: requires publicationId from list_blogs or create_publication, voiceProfileId from list_voices, and explains the async workflow with next steps (poll status, retrieve, edit, publish). It doesn't explicitly say when not to use this tool versus alternatives, but gives strong contextual guidance.

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