createTagGroup

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

Annotations already indicate this is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds crucial behavioral context: it confirms writes live data, reveals that the system does NOT enforce uniqueness on group_tag_name, and provides specific pre-check instructions to prevent duplicate creation. This goes beyond annotations to guide safe usage.

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 well-structured with clear sections: purpose, usage context, required parameters, pre-check logic, and see-also. It is front-loaded with the core action and remains concise without unnecessary fluff. Every sentence adds value.

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 simple create tool, the description covers the essential context: purpose, when to use, parameter requirements, critical pre-check for uniqueness, and alternative actions. No output schema exists, but given the tool's simplicity, the description is complete and actionable.

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 compensate. It lists the required parameters (group_tag_name, added_by, updated_by) and explains group_tag_name's role and uniqueness issues. However, it does not define added_by and updated_by (likely user IDs), leaving some ambiguity. Partial but beneficial explanation.

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 clearly states the tool creates a new tag group record and writes live data. It specifies the resource (tag group) and action (create), distinguishing itself from siblings like listTagGroups and updateTagGroup.

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 explicitly states when to use the tool ('organizing tags into new themes, rare') and includes a pre-check requirement to avoid duplicates, directing to use updateTagGroup if the name exists. It provides clear alternatives and conditions.

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