wetrack_delete_metadata_field

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

With no annotations, the description carries the behavioral disclosure burden. It adds a useful non-obvious failure condition ('Will fail for system-protected fields') but does not disclose other destructive traits like irreversibility or potential cascading effects on tickets using the field.

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 compact and front-loaded: action, critical caveat, then the single parameter. Every sentence adds value without redundancy.

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?

For a simple one-parameter delete operation, the description is nearly complete: it names the target, explains the argument, and warns about protected fields. The output schema covers return values, so the main omission is additional detail on the consequences of deletion.

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%, so the description must define the parameter. The Args section explains 'field_id' as 'Integer ID of the metadata field to delete,' adding semantic context beyond the bare schema type and title.

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 states a specific action and resource: 'Delete a metadata field definition.' This is clear and distinct from metadata field get/list/create/update/toggle siblings, though it does not explicitly name a sibling it is not.

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?

The description implies usage when a metadata field definition must be permanently removed, and provides a when-not warning: 'Will fail for system-protected fields.' However, it does not mention alternatives such as toggling a field's status or when to prefer update over delete.

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