Search Tracker employee absences

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

Goes beyond the annotations (readOnlyHint, idempotentHint, openWorldHint) by disclosing that the read is issued via POST, that Tracker administrator rights are required, and that every requested user is returned with an empty gaps list when not absent. That auth requirement and result-shape guarantee are real added value.

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 tightly written sentences; the resource definition is front-loaded and the operational caveats (POST read, admin rights, empty-list behavior) follow without padding.

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 read-only, non-destructive search with full schema coverage and no output schema, the description supplies the key missing context: permissions, transport quirk, and the guarantee that non-absent users still appear. Only minor details like pagination/cap behavior are left to the schema.

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 100%, so users, limit, date_from and date_to are already documented in the schema. The description reinforces the window-overlap semantics and the multi-user batch nature but adds no format or edge-case detail beyond the schema.

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 resource (employee absences/gaps) with concrete examples of absence types and a clear scope (given users, overlapping a window). It is distinguishable from sibling write tools like tracker_gaps_create, though it never names an alternative explicitly.

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?

Usage is implied by the purpose: batch-lookup absences for a supplied list of users over a time window. There is no explicit when-to-use/when-not or comparison against siblings such as tracker_users_get or tracker_gaps_create, so guidance stays at the implied level.

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