create_tag

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

No annotations, so description carries full burden. Discloses key behaviors: tag creation, optional folder, no delete API. Could add detail on name uniqueness or permissions, but sufficient for basic transparency.

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?

Three concise sentences with no redundancy. Each sentence adds distinct information: action, folder behavior, delete limitation.

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?

Missing output schema description—no mention of return value (e.g., created tag ID). Also lacks name format constraints or uniqueness. Adequate for basic use but incomplete for full context given its criticality as a creation tool.

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%, and description adds value by stating folder_id default behavior (unclassified folder) not in schema. Enhances understanding beyond parameter descriptions.

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?

Description clearly states '新しいタグを作成する' (create a new tag), with specific verb and resource. It also clarifies folder behavior and absence of delete API, distinguishing it from siblings like add_tag_to_friend and create_tag_folder.

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 guidance on folder_id default, but lacks explicit when-to-use vs alternatives. Does not mention prerequisites or scenarios for this tool versus create_tag_folder or bulk_add_tag.

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