Move a custom field option

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

No annotations exist. The description does not disclose any behavioral traits such as whether the move is destructive, reversible, or requires specific permissions. It only states the action without additional 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 short but includes a verbose endpoint URL that may not be helpful for an AI agent. It is concise but could be more effective by summarizing key constraints instead of duplicating the HTTP method and path.

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 no output schema, no annotations, and two nested objects with required fields, the description is incomplete. It omits crucial details like the need to provide either after or before, and the effect of the move on the option order.

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 0%, so the description must compensate. It fails to explain the required parameters (funnel_id, custom_field_id, id, after, before) or the constraint that after and before are mutually exclusive. The schema has descriptions for body properties, but the description adds nothing.

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 states 'Move a custom field option,' which clearly indicates the verb and resource. However, it does not differentiate from sibling tools like weeek_move_a_custom_field_option or weeek_move_a_custom_field_option_2, leaving the agent unsure which variant to use.

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 versus alternatives. There is no mention of prerequisites, when-not to use, or context for the move operation.

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