create_tag

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

With no annotations provided, the description must fully disclose behavioral traits, but it does not. It fails to mention idempotency (whether duplicate tags can be created), required permissions, or any side effects. The existence of an output schema is not leveraged in the description.

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 very concise, consisting of two short sentences with no extraneous information. The key action and a critical parameter are front-loaded. Slightly more structure (e.g., bullet points for parameters) could improve readability.

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?

Despite the tool being simple (3 parameters, output schema exists), the description leaves gaps: no mention of duplicate handling, whether tag_name must be unique, or any errors. The output schema is not referenced, so agents may not know what the response contains.

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 description clarifies the 'tag_type' parameter by specifying 'contact or deal', adding meaning beyond the schema (which only shows default and type). However, 'tag_name' and 'description' are not elaborated; their meaning is inferred from context. Given 0% schema coverage, this is a 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 'Create a new tag' and explicitly lists the allowed values for tag_type ('contact or deal'), making the purpose and scope immediately clear. It distinguishes itself from sibling tools like add_tag_to_contact by focusing on creation rather than assignment.

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?

No guidance is provided on when to use this tool vs alternatives (e.g., when to create a new tag vs using an existing one). There is no mention of prerequisites, best practices, or scenarios where this tool is appropriate.

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