tc_create_group

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

Beyond the annotations (readOnlyHint=false), the description adds the TC_ENABLE_WRITE=1 requirement and the return format {'created': true}, providing useful behavioral context not covered by structured data.

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 concise and well-structured: purpose, prerequisite, args, and return value are each covered in a clear, front-loaded manner with no redundant text.

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 operation, it covers the essential aspects: purpose, prerequisite, args, and return. It does not detail error scenarios or side effects, but given the tool's simplicity and the output schema mention, this is adequate.

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?

The input schema has no descriptions (0% coverage), but the description explains both parameters with examples (e.g., group name), fully compensating for the schema's lack of detail.

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 'Create a user group in a project' with a specific verb (create) and resource (user group), clearly distinguishing it from siblings like tc_list_groups, tc_rename_group, and tc_delete_group.

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?

Provides clear context for creating a user group and mentions the prerequisite TC_ENABLE_WRITE=1. However, it does not explicitly discuss when not to use this tool or mention alternatives, but the purpose itself implies the usage.

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