Delete a custom field

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

The description implies deletion (a destructive action) but does not disclose any side effects, access requirements, or reversibility. With no annotations, the description must provide more context.

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, which is concise, but it could include more useful information without becoming verbose. The structure is minimal but acceptable.

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 lack of output schema and 0% schema description coverage, the description is insufficient. It does not explain what happens after deletion (e.g., response) or any constraints on the custom field.

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%. The parameter 'path' contains board_id and id, but the description only repeats the URL pattern without explaining what these identifiers represent or where to find them.

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 a custom field' and includes the HTTP method and URL, making the action obvious. However, it does not differentiate from sibling tools weeek_delete_a_custom_field and weeek_delete_a_custom_field_3, which likely have identical 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 (e.g., when to choose this over other delete custom field tools). There are no prerequisites or exclusions mentioned.

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