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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so 'destructive write operation' merely restates structured data rather than adding value. The description omits what is actually destroyed (field values on existing tasks/entities), whether deletion is recoverable, and any auth/permission requirements.

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?

Two short sentences, front-loaded with the action and endpoint. The second sentence is largely redundant with the annotations but costs little; nothing is padded or buried.

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 destructive, non-idempotent delete with a mandatory confirm parameter and no output schema, the description covers the mechanics but not the consequences. An agent knows what it does but not what data is lost or whether the operation is reversible, which is material for an irreversible delete.

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 86%, so the schema already documents confirm, credentials, and base_url. The description only implies custom_field_id via the URL template and adds no new semantics for the remaining parameters, so baseline 3 applies.

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?

States a specific verb (Deletes) and resource (custom field definition) and even names the endpoint path, so the action is unambiguous. It does not explicitly differentiate from siblings like delete_enum_option or update_custom_field, but the resource noun is distinctive enough to identify the target.

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?

There is no guidance on when to use this tool versus alternatives (e.g. delete_enum_option, update_custom_field, archive_* patterns). No prerequisites, no note that the field must exist, and no mention of the required confirm flag as a usage condition.

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