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

With readOnlyHint=false, idempotentHint=false and destructiveHint=false already declared, the description adds real value by disclosing a hard quota (12 tabs per folder) and by stating the response contains the entire updated library. It does not say what happens when the cap is exceeded (error vs silent failure), which keeps it from a 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?

Two short sentences, front-loaded with the action and then the two constraints an agent needs (quota, response payload). No filler and nothing redundant.

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 two-parameter creation tool with no output schema, the description covers the essential extras: the per-folder limit and the fact that the response already contains the refreshed library, saving a redundant GET /api/library. Only the failure behavior at the quota boundary is left unstated.

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% — both category_id and name are fully documented in the schema, including the 40-character limit and the cat_… prefix. The description adds no parameter-level information, so the baseline 3 is appropriate.

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 gives a specific verb+resource ("Creates a tab in a folder") and its scope, which is enough to separate it from the folder-creating sibling create_category. It would be a 5 if it resolved the mismatch between the tool name create_group and the user-facing term "tab".

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?

Usage is implied by the constraint ("12 tabs at most per folder") and the location phrase, but there is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The 12-tab cap is the only routing signal an agent gets.

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