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

Beyond the annotations, the description discloses two meaningful behavioral details: the subdomain is auto-generated from the name, and specific auth credentials are required. These add practical context that helps an agent anticipate setup and side effects, though it does not describe every possible failure mode.

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 is two sentences with no filler: it states the action, the key auto-generation behavior, and the auth requirement. Every sentence contributes actionable information, and the most important details are front-loaded.

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 3-parameter creation tool with an output schema and annotations, the description is complete. It covers the core purpose, the auto-generated subdomain behavior, and auth requirements. Nothing essential about how to invoke the tool is missing.

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?

The input schema already covers all three parameters with descriptions, so the baseline is 3. The description adds extra meaning to the 'name' parameter by stating that the subdomain is auto-generated from it, which goes beyond the schema's simple 'Blog name' description.

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 a specific verb and resource, 'Create a new blog,' making the tool's purpose immediately clear. The blog resource is distinct from sibling create_* tools like create_post and create_collection, and there is no ambiguity about what is being created.

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 description clearly indicates this tool creates a new blog and provides an important usage prerequisite: it requires account-level OAuth or a user-scoped API key. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for an agent to select it for creating a blog.

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