Delete Tracker filter

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the 'permanently/irreversible' phrasing largely restates structured data. It does add one piece of genuinely new context – 'Returns an acknowledgement on success' – which is useful since there is no output schema, but it omits error behavior for a missing filter and whether deletion cascades.

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 destructive action and scope, with no filler. Every clause carries weight.

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 single-parameter deletion with rich annotations and no output schema, the description covers the essentials and helpfully notes the acknowledgement response. It falls short only on failure modes and permissions, which an agent might need before calling.

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 100% and the schema itself gives the filter_id format and an example ('12345'). The description adds nothing about the parameter, so the baseline 3 applies since the schema carries the load.

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 and resource ('delete a saved issue filter') with clear scope, and the name/description pair cleanly distinguishes it from the sibling tracker_filters_get, tracker_filters_create, and tracker_filters_update.

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 delete versus other filter operations, no prerequisites (e.g. ownership or admin rights), and no hint about how an agent obtains the filter_id since no tracker_filters_list sibling exists. The agent must infer the workflow entirely.

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