create_blog_post_draft

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

No annotations are provided, so the description carries the transparency burden. It does add one key behavioral fact: the post is created in DRAFT state and is not publishd immediately. But it does not disclose permission requirements, duplicate-slug behavior, validation rules, or side effects on existing resources.

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?

The description opens with a one-sentence purpose and follows with a compact, structured Args list. There is no filler; each line adds operational information an agent needs.

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 9-parameter tool with no annotations and an output schema present, the description is nearly complete: it explains all parameters, supplies format constraints, and points to sibling lookup tools. It is only missing explicit handling notes for edge cases like duplicate slugs or invalid tag IDs.

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 0%, so the description must compensate, and it does. Each parameter receives a meaningful hint beyond its name: slug format, language default, HubSpot-hosted image requirement, and references to list_blogs and list_blog_authors for ID lookup.

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 names a specific resource ('blog post'), a clear verb ('Create'), and a distinctive state ('DRAFT'). It is immediately distinguishable from sibling tools like create_landing_page_draft, create_site_page_draft, and update_blog_post_draft.

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 state' phrasing implies this is the tool for creating a new, unpublishd blog post rather than updating or publishing one. However, it never explicitly states when not to use it or names alternatives, so routing guidance is only implied.

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