conduyt_create_tag

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

No annotations are provided, so the description carries the full burden. It does disclose one genuine behavioral trait that matters for a mutation tool — duplicate names are rejected — but it says nothing about authentication requirements, whether the rejection is an error versus a silent no-op, or idempotency, which is a real gap for a create operation.

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?

Two short sentences, zero padding, with the action front-loaded before the constraint. Nothing extraneous and nothing buried.

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 simple two-parameter create tool with no annotations and no output schema, the description covers the purpose and the one notable failure mode. It stops short of explaining what is returned (e.g., the new tag's ID) or any permission requirements, which are modest but real omissions.

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%: the name uniqueness constraint and the color hex format with its default are documented in the schema itself. The description adds no syntax, format, or constraint detail beyond it, so the baseline 3 applies.

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?

States a specific verb and resource ("Create a new tag"), which cleanly distinguishes it from conduyt_update_tag, conduyt_delete_tag, and conduyt_merge_tags by verb. It does not explicitly address the tagging siblings (conduyt_add_tags, conduyt_add_deal_tags), so an agent must infer from the names that those apply tags to records rather than define a tag.

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?

There is no statement of when to use this versus alternatives, nor prerequisites or ordering. The only implicit hint is "Rejects duplicates," which tells the agent it need not pre-check existence, but that is a side effect rather than usage guidance.

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