Delete Tracker employee absences

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

Goes meaningfully beyond the annotations: annotations declare destructive/non-idempotent, but the description adds that the deletion is irreversible, that unknown ids are silently ignored, that admin rights are required, and that it returns an acknowledgement. The 'unknown ids ignored' detail is genuinely useful non-obvious behavior.

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 tight sentences with zero waste; the irreversible warning and the id-sourcing hint are front-loaded before the permission requirement. Every sentence carries information.

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?

With no output schema, the description usefully notes the return is an acknowledgement, and it covers the destructive/irreversible nature and the admin prerequisite. A minor gap is not pointing to tracker_gaps_search for obtaining ids, but the essentials are present.

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 single gap_ids parameter is well documented (up to 100 ids, sourced from a search). The description adds little beyond the schema, so the 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 (Delete) and resource (employee absences) scoped by id, which clearly separates it from tracker_gaps_search and tracker_gaps_create. Sibling differentiation is implied by the verb rather than stated explicitly, so it falls just short of a 5.

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?

Provides a prerequisite (Tracker administrator rights) and the schema hints ids come 'from a search', but the description never explicitly says when to use this vs. alternatives or that ids should be obtained from tracker_gaps_search first. Usage is implied rather than spelled out.

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