Move global custom field option

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the action and endpoint, omitting details about side effects (e.g., reordering, persistence), required permissions, or idempotency. This is insufficient for a mutation tool.

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 unnecessary technical details (HTTP method, tags) that are not helpful for an AI agent. It could be more natural and focused. Still, it is not overly verbose.

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 the complexity (nested objects, sibling tools) and lack of output schema, the description is missing context such as what 'global' means versus regular custom field options, and how moving affects the UI. The agent may not understand when to use this tool.

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 input schema already provides descriptions for parameters like 'after' and 'before', including mutual exclusivity. The tool description adds no parameter-level information. With schema coverage at 0% (meaning the tool description doesn't cover parameters), the description does not compensate, but the schema itself is adequate, so score is baseline 3.

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 global custom field option' which clearly indicates the action and resource. However, it does not differentiate from sibling tools like weeek_move_a_custom_field_option, which may cause confusion. The inclusion of technical details like endpoint and tags is extraneous.

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 provides no guidance on when to use this tool versus alternatives such as weeek_move_a_custom_field_option or weeek_move_a_custom_field_option_2. An agent would have to infer the difference from the tool name alone.

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