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

The description's 'Create a new collection' is consistent with annotations indicating a non-read-only, non-idempotent, non-destructive write operation. It adds little beyond the annotation profile, such as duplicate behavior, validation failures, or side effects, but it does not contradict the annotations.

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 a single sentence with no filler, front-loading the core action and the key fields. Every word earns its place.

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 schema fully documents all parameters, including the required blogId and its discovery path, annotations describe the mutation profile, and an output schema exists. The only minor gap is that blogId is absent from the natural-language description, but the schema compensates completely.

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 100%, and the schema already provides good semantic detail, including the blogId hint to use list_blogs. The description merely repeats name, slug, and description names while omitting blogId, so it adds no meaningful semantic value beyond 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 states a specific verb and resource ('Create a new collection') and lists the main fields (name, slug, optional description), distinguishing it from update_collection and delete_collection. It is clear but omits blogId from the prose, and it largely restates the title with a bit more detail.

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 gives no guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites beyond what appears in the schema. There is no explicit routing to sibling tools like update_collection or list_collections.

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