Create dropdown value

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

The description discloses key positioning behavior ('appended at the end unless you give a position'), but with no annotations provided, it should also cover potential destructiveness, required permissions, or side effects. It partially fulfills the behavioral disclosure burden.

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 with no wasted words. The core action is front-loaded, and the important positioning detail follows immediately. Every sentence serves a purpose.

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 5 parameters, no output schema, and no annotations, the description covers the primary behavior and positioning nuance. However, it omits return value information (e.g., what is returned on success) and any required permissions or side effects. Adequate but not fully complete for confident agent invocation.

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 description coverage is 100%, so baseline is 3. The description adds minimal parameter context by mentioning position behavior (relating to insert_after/insert_before), but does not explain individual parameters beyond what the schema already provides.

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 the action ('Add a value') and the target resource ('enum / multi_enum custom field'), distinguishing it from sibling tools like enum_option_update and enum_option_reorder.

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 implies when to use (when you need to add a dropdown value) but does not provide explicit guidance on alternatives (e.g., using enum_option_update to modify existing options) or exclusion criteria. No when-not guidance is given.

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