Delete a custom field

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

The description implies destruction via 'DELETE' but does not disclose irreversibility, side effects, or authentication needs. Without annotations, more detail is expected.

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 redundant HTTP path information. It could be more concise by omitting the path and focusing on usage context.

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 presence of sibling deletion tools and no output schema, the description fails to provide sufficient context about effects, undoability, or scope. It lacks completeness for a deletion operation.

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 input schema has 1 parameter (path) with nested properties (project_id, id), but schema description coverage is 0%. The description does not explain these parameters beyond stating the action, so it adds negligible 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 a custom field' and includes the HTTP method and path, providing a clear verb+resource. However, it does not distinguish between this tool and siblings like weeek_delete_a_custom_field_2 and _3.

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 given on when to use this tool versus the alternatives. The description lacks any context about prerequisites, scenarios, or exclusions.

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