hcp_create_tag

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

Annotations already establish this is a non-read-only, non-destructive write operation. The description adds valuable behavioral context beyond annotations by disclosing that duplicate names return 422 and that tag names are case-sensitive, which meaningfully affects invocation and error handling.

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 only two short sentences with no wasted words. The primary action is front-loaded, and the key behavioral details follow immediately. 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?

For a one-parameter creation tool with an output schema and clear annotations, this description is complete enough for correct invocation. It conveys the action, the uniqueness rule, and the case-sensitivity rule. No critical missing information appears for an agent to select and call it properly.

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 schema provides no description for the required 'name' parameter, so the description must carry semantic weight. It does so by clarifying that names are case-sensitive and that duplicates are rejected, giving the agent important constraints that the schema alone omits.

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 operation ('Create a new tag.') with a specific verb and resource, and it distinguishes the tool from siblings like hcp_apply_tag_to_job and hcp_apply_tag_to_customer. The additional duplicate and case-sensitivity details further clarify the tool's unique purpose.

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 intended use is implied: use this when a new tag needs to be created before applying it to jobs or customers. However, there is no explicit guidance about when not to use this tool or when to prefer a sibling such as hcp_list_tags to check existing tags first.

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