hcm_search_absences

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

The readOnlyHint annotation already conveys that this is a safe read operation, and the description's 'Search' wording is consistent with that. However, the description adds no behavioral detail beyond the annotation: it does not say whether results are paginated, what fields are returned, or how the query string behaves.

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 short and has no redundant words, but it is under-specified to the point of essentially restating the tool name. It is concise without being informative, so it does not meet the bar for an appropriately sized tool description.

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?

The tool has three parameters with no schema descriptions, no output schema, and a large sibling toolset, yet the description provides none of the context needed to call it correctly. An agent cannot tell what a valid q looks like, what the result set contains, or how absences relate to the other absence-related sibling tools.

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 compensate for the undocumented q, limit, and offset parameters. It does not: 'Search absences' gives no meaning for q, no indication of pagination semantics, and no hint about what absence fields or values the parameters accept.

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 provides a specific action ('Search') and a resource ('absences'), so the agent can tell this is a read-oriented discovery operation over absence records. It does not elaborate on how it differs from hcm_get_absence or hcm_search_absence_plans, but the core purpose is clear.

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 about when to use this tool versus alternatives. It does not mention that hcm_get_absence is for retrieving a single known absence, nor does it explain when searching is appropriate or how limit/offset relate to result pagination. The agent is left to infer usage entirely from the name.

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