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

Annotations cover the safety profile (readOnlyHint=false mutation, destructiveHint=false, openWorldHint=true), but the description adds valuable context the annotations lack: the slug auto-generation behavior and the fact that the thumbnail URL is fetched and uploaded to the project CDN (an external side effect). It stops short of disclosing auth/permission needs or duplicate-name behavior, so a 4 rather than 5.

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?

Purpose is front-loaded in the first sentence, followed by a well-organized Args list where each entry earns its place given the 0% schema coverage. Minor redundancy between the summary ('Name is required') and the Args entry ('required') prevents a 5.

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 an 8-param mutation with an output schema (so return values need no explanation) and annotation coverage, the description is nearly complete. It omits auth requirements and error/duplicate handling, which are the remaining gaps.

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 carry the full parameter burden and largely does: it documents all 8 args, marks name as required, explains the slug default, and notes that the three thumbnail_* fields are stored in thumbnail_meta. It lacks detail on empty-string defaults or format constraints, keeping it below 5.

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?

States a specific verb+resource ('Create a new CMS post category'), clearly distinguishing it from siblings like create_cms_post, create_commerce_collection, and update_cms_category. An agent can identify the target entity without opening the schema.

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 implies usage through required/optional semantics ('Name is required; slug is auto-generated from name if omitted') but never states when to reach for this tool versus create_cms_post or the other create_* siblings. No exclusions or alternative routing are given.

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