create_contact_field

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

With no annotations provided, the description must disclose behavioral traits, but it only repeats the basic action. It does not mention permissions, side effects, validation rules, or what happens on duplicate names. This leaves the agent without critical operational context.

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 brief with a single sentence, but this brevity results from under-specification rather than efficient communication. It omits essential details about the parameter and behavior, so it is not 'appropriately sized'.

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?

The tool has a nested object parameter, no output schema, and no annotations, but the description provides no additional context about return values, field schema, or integration with other field-management tools. It is insufficient for an agent to invoke the tool with confidence.

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 single required parameter `contact_field_fields` has no description in the schema (0% coverage) and the tool description does not mention it. The parameter is an object expected to contain field configuration, but the agent cannot infer its structure or required keys.

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?

Description clearly states the action ('Create') and the resource ('a contact field in Freshdesk'), which distinguishes it from sibling tools like create_ticket_field and update_contact_field. It is specific and unambiguous.

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 about when to use this tool, prerequisites, or alternative tools. The description only states the action, so the agent lacks context for choosing between creating vs updating a field or using related field-management tools.

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