create_contact_field

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 that presentation_json is required for number/datetime fields, which is useful, but it does not mention side effects, irreversibility, permissions, or any other behavioral traits. For a mutating create operation, this is a gap.

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 a compact, well-organized list. The purpose is front-loaded, and each parameter description is terse yet complete, with no fluff or redundancy.

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 7 parameters and no schema descriptions, the description covers all of them accurately, including conditional requirements. The presence of an output schema means return values need not be explained, so the description is fully sufficient for an agent to invoke the tool correctly.

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?

With 0% schema description coverage, the description fully compensates by detailing every parameter: name length, field_kind enum values, tab_id purpose, presentation_json format with example, optional group_id/insert_after, and multiples semantics. This goes well beyond the bare schema.

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 begins with 'Create a new custom contact field,' using a specific verb ('Create') and resource ('custom contact field') that clearly distinguishes it from sibling tools like update_contact_field, delete_contact_field, and list_contact_fields.

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 use case is implied by the name and opening line: use this when you need to create a new contact field. However, there is no explicit guidance about when not to use it or how it differs from related tools like create_contact_field_group or create_contact_field_tab.

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