Delete global custom field

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

No annotations are present, so the description must provide behavioral context. It only says 'Delete', which implies a destructive mutation, but it does not disclose side effects (e.g., whether the field is removed from all tasks), authentication requirements, or irreversibility. This is insufficient for safe agentic use.

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 (two sentences plus a tag), which is concise but lacks necessary detail. It is front-loaded with the endpoint and action, but the brevity comes at the cost of completeness. Every sentence is earned, but more information is needed.

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 of multiple sibling delete tools, the description does not provide enough context to distinguish this global field deletion from others. No output schema is provided, and the parameter is not explained. The description is incomplete for effective tool selection and invocation.

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 schema has 0% description coverage and only one parameter 'path.id', which can be a string or number. The description adds no explanation about what this ID represents (e.g., the custom field identifier). Without this, an agent cannot correctly construct the parameter 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 'Delete global custom field' and provides the HTTP method and path. The verb 'Delete' indicates the action and the resource is explicit. However, it does not differentiate from siblings like weeek_delete_a_custom_field, which also delete custom fields but at different scopes.

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 alternative delete tools for custom fields. Given many sibling tools with similar names, an agent would need to know that this tool is specifically for global custom fields, but the description does not offer such context or exclusions.

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