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

Annotations already declare destructiveHint=false, readOnlyHint=false, and idempotentHint=true. The description adds useful specificity beyond the annotations by identifying slug as the idempotency key and stating that an existing group is returned rather than an error being raised.

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 with no waste. The core action is front-loaded and the idempotency behavior follows immediately.

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 tool is simple, schema descriptions are complete, annotations are rich, and an output schema exists. The description covers the key creation behavior and conflict handling, though it does not discuss tenant scoping or permissions, which are handled by the schema and surrounding tools.

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 coverage is 100%, so the baseline is 3. The description adds semantic value by making slug the idempotency key, which is not obvious from the schema's 'URL slug; auto-generated from name if absent' alone.

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 and resource ('Create a group'), which clearly distinguishes it from sibling operations like kb_groups_update, kb_groups_delete, kb_groups_get, and kb_groups_list.

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?

Explains the key behavioral condition for calling it: idempotent on slug, returning the existing group if the slug already exists. This tells an agent it can safely create without checking first, though it does not explicitly name alternatives such as kb_groups_update for modification.

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