Create Custom Field

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

Annotations already indicate a write operation (readOnlyHint=false) and non-destructive behavior (destructiveHint=false). The description adds useful context that enum options are added separately and that the created object is returned, but it does not disclose other behaviors like permissions or irreversibility of type.

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?

Three sentences, no fluff. The first sentence states main purpose and types, the second handles enum options, and the third states the return value, all efficiently.

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 10-parameter creation tool with no output schema, the description covers the core action, supported types, return value, and the enum option follow-up. It does not list all parameters but relies on the schema, and it omits workspace default behavior, which is already in the schema. This is adequate but not exhaustive.

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%, with each parameter documented. The description adds a meaningful note about enum option workflow but otherwise repeats type values already present in the schema, so it does not significantly enrich parameter understanding.

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 field in a workspace," using a specific verb and resource. It distinguishes from sibling tools like asana_update_custom_field and asana_create_enum_option by explicitly focusing on creation and referring to the separate option-adding step.

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 description gives explicit guidance for enum/multi_enum fields, directing users to asana_create_enum_option for adding options. However, it does not state when to use this tool versus other custom field tools like update or delete, though that is largely implicit.

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