tc_rename_group

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive nature (destructiveHint=false). The description adds value by disclosing the TC_ENABLE_WRITE=1 requirement and the return format with {"renamed": true}, which are not in annotations. This provides meaningful behavioral context beyond the 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 highly concise, with four short sections: purpose, requirement, args, and return. It front-loads the main verb and includes no filler or irrelevant information. Every sentence earns its place.

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?

Given the low complexity (three required string parameters, no enums) and the presence of an output schema, the description is largely complete. It covers the core purpose, the write requirement, and the return signature. It doesn't address error conditions, but this is minor for a simple rename operation with available annotations and schema.

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 0% description coverage, so the description must compensate. However, the Args section merely restates the parameter names ('Project ID', 'Group ID', 'New group name') without any additional details such as where to obtain the IDs, uniqueness constraints, or format requirements. This fails to add meaning beyond the schema's property names.

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 opens with 'Rename a project group.' which is a specific verb+resource statement that clearly distinguishes this tool from siblings like tc_rename_item, tc_create_group, and tc_delete_group. The scope is unambiguous.

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 provides clear context for when to use the tool (renaming a project group) and states a prerequisite (TC_ENABLE_WRITE=1). It does not explicitly mention alternatives or exclusions, but the tool name and description make the intended use unambiguous, so it meets the 'clear context' bar.

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