blogs_create_blog_post

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

The description adds no behavioral information beyond the name. Annotations indicate a write operation (readOnlyHint=false) but the description does not disclose side effects, requirements, or potential pitfalls. It offers zero value beyond the structured metadata.

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?

While the description is extremely brief, this is under-specification rather than effective conciseness. It lacks the substance needed for a tool with 14 parameters and 11 required fields.

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 create operation with complex requirements, the description is severely incomplete. It does not mention output behavior, required field dependencies, or any important constraints, despite having no output schema to rely on.

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 only 36%, and the description does nothing to compensate. It explains no parameters, leaving agents without guidance on how to fill required fields like rawHTML, urlSlug, or imageAltText, which are not described in the 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?

The description 'Create Blog Post' merely restates the tool name, providing no additional information about the action, resource, or scope. It does not distinguish this from sibling tools like blogs_update_blog_post or blogs_get_blog_post.

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?

No usage context is provided. There is no guidance on when to use this tool versus alternatives, no prerequisites, no mention of required external lookups (e.g., author ID, category ID) that are critical for correct invocation.

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