Transfer custom field to task manager

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without revealing side effects (e.g., whether the original custom field is deleted), required permissions, or response format. The HTTP method POST hints at creation but is insufficient.

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 very short—a single line with endpoint and a sentence. It is concise but lacks structure or important details. The 'Tags: Board' adds minimal context. It does not waste words, but is too minimal to be well-organized.

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 absence of annotations and output schema, the description should cover behavior, parameters, and effects. It only mentions the action and endpoint. For a tool that likely modifies board data, this is incomplete and risks misuse.

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%, meaning the description adds no explanation of parameters. The endpoint path places {board_id} and {id} are noted, but their meanings are not clarified. The schema defines them as required, but the agent must infer their roles, which is inadequate for correct invocation.

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 'Transfer custom field to task manager' and includes the endpoint path, indicating the action and resource. However, it does not explain what 'transfer' entails (move vs. copy) or distinguish between similar sibling tools like weeek_transfer_custom_field_to_task_manager (without _2). Purpose is clear but ambiguous.

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. With many sibling tools for transferring custom fields to different destinations, the agent lacks context for selection. No prerequisites or exclusions are mentioned.

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