Transfer global custom field to project

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

No annotations provided. Description does not disclose side effects (e.g., whether the global field is deleted from its original scope, how existing data is affected, or any irreversible changes). For a mutation, this 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 short and gets to the point, but includes unnecessary technical details ('POST /tm/custom-fields/{id}/transfer-to-project' and 'Tags: Custom fields') that clutter it. It could be more concise by focusing on the core action.

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 annotations, no output schema, and two parameters with nested objects, the description is incomplete. It does not explain the return value, prerequisites, or consequences of the transfer. The agent cannot fully understand the tool's behavior.

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% and the description does not explain the parameters. It only mentions 'Body: application/json', but does not describe the 'path' or 'body' structure beyond what the schema provides. The schema itself is self-explanatory but the description adds no value.

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 'Transfer global custom field to project', specifying the verb, resource, and target. It distinguishes from sibling tools that transfer regular custom fields (e.g., weeek_transfer_custom_field_to_project) by including 'global'.

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 on when to use this tool versus alternatives like weeek_transfer_custom_field_to_project. Does not explain what a global custom field is or provide context for when a transfer is appropriate.

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