create_tag

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

Annotations already declare readOnlyHint=false (write operation) and destructiveHint=false, so the description does not need to restate that. However, it adds no extra behavioral context such as required permissions, what happens on duplicate names, or rate limits. The description is minimal and contributes no additional transparency beyond annotations.

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 (four words), but it is too brief to be informative. Conciseness should not sacrifice necessary details. A single line is appropriate, but it should include key usage hints.

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 tool's complexity (nested object with 6 parameters and no schema descriptions), the description is woefully incomplete. Although an output schema exists, the description does not mention what the tool returns (e.g., the created tag object). The description fails to provide essential context for correct invocation.

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%, meaning the input schema lacks any property descriptions. The description 'Create a new tag' does not compensate by explaining any parameters, leaving the six properties (name, color, match, is_inbox_tag, is_insensitive, matching_algorithm) completely undocumented. This is a critical gap.

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 states exactly what the tool does: 'Create a new tag.' It uses a specific verb and resource, clearly distinguishing it from sibling tools like create_correspondent or create_document_type. However, it does not elaborate on any specific scope or constraints, missing an opportunity for full clarity.

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 no guidance on when to use this tool versus alternatives such as bulk_edit_tags or update_tag. There is no mention of prerequisites, context, or exclusions, leaving the agent without decision-support.

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