ticktick_create_tag

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

Annotations already indicate this is a non-readOnly, non-idempotent, non-destructive operation. The description adds valuable context beyond annotations by specifying authentication requirements ('Requires v2 API authentication') and nesting behavior ('Tags can be nested by specifying a parent tag name'). It doesn't contradict annotations and provides useful implementation details.

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 extremely concise with just three sentences, each delivering essential information: core purpose, nesting capability, and authentication requirement. It's front-loaded with the main action and wastes no words. Every sentence earns its place by adding distinct 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?

Given that there's an output schema (which handles return values), annotations cover safety profile, and the tool has only 1 required parameter, the description provides adequate context. It covers authentication requirements and nesting behavior which aren't in structured fields. For a simple creation tool with good annotations and output schema, this is reasonably complete.

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, but the description doesn't mention any parameters directly. However, it implicitly explains the purpose of the 'parent_name' parameter through 'Tags can be nested by specifying a parent tag name'. This adds some semantic value, but doesn't cover 'name' or 'color' parameters. With 0% schema coverage, the description provides partial compensation.

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 action ('Create a new tag') and resource ('tag'), making the purpose immediately understandable. It distinguishes from siblings like 'ticktick_rename_tag' or 'ticktick_delete_tag' by specifying creation rather than modification or deletion. However, it doesn't explicitly differentiate from 'ticktick_merge_tags' which also involves tag operations.

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 implied usage context through 'Tags can be nested by specifying a parent tag name' and 'Requires v2 API authentication', suggesting when to use nesting and authentication prerequisites. However, it lacks explicit guidance on when to choose this tool over alternatives like 'ticktick_update_tag' or 'ticktick_merge_tags', and doesn't mention any exclusions or specific scenarios.

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