Move a custom field option

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

No annotations are present, so the description carries the full burden. It only mentions the HTTP method and endpoint, omitting side effects, permissions, or constraints (e.g., the mutual exclusivity of 'after' and 'before' is not stated). The description is insufficient for safe usage.

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 extraneous elements like 'Tags: Board' and 'Body: application/json' that add little value. It is not front-loaded with the most critical information and could be more structured.

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 only two parameters with minimal description, the tool definition is incomplete. The agent lacks information about return values, error conditions, or the effect of the move operation, leaving significant gaps.

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?

Despite the schema having descriptions for 'after' and 'before', the description adds no extra meaning. It does not explain the path parameters (board_id, custom_field_id, id) or clarify the relationship between 'after' and 'before'. With 0% schema description coverage (as per context), the description fails to compensate.

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 'Move a custom field option' and includes the HTTP method and endpoint. However, it does not differentiate from sibling tools like weeek_move_a_custom_field_option and weeek_move_a_custom_field_option_3, which have identical titles and descriptions.

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 are multiple similar sibling tools (e.g., weeek_move_a_custom_field_option, weeek_move_a_custom_field_option_3) with no distinguishing context, leaving the agent without decision criteria.

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