Delete a custom field

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

The description only states 'Delete a custom field' and 'Tags: Funnels', with no annotations to rely on. It fails to disclose behavioral traits such as whether the deletion is permanent, reversible, or has side effects on related data. A deletion operation demands more transparency than provided.

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 brief (two sentences) and front-loaded with the HTTP path, but it is under-stuffed for the information needed. Every sentence should earn its place; here, 'Tags: Funnels' adds minimal value.

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 tool complexity (deletion, multiple similar siblings, nested parameters), the description is inadequate. It does not explain how this tool differs from other delete custom field tools, nor does it mention return values or side effects. No output schema exists to compensate.

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 coverage is 0% and the description adds no meaningful explanation for the parameters (funnel_id, id). It mentions them in the path but does not clarify their purpose, accepted values, or constraints. The schema's type definitions (string or number) are not supplemented.

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, reinforcing the deletion purpose. However, it does not distinguish this tool from sibling delete custom field tools (weeek_delete_a_custom_field, weeek_delete_a_custom_field_2), lacking specificity on what makes this variant unique (e.g., context, scope).

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 the other delete custom field tools or other sibling tools. There is no mention of prerequisites, alternatives, or exclusions, leaving the agent without context to choose appropriately.

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