hcm_search_element_entries

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

Annotations already declare readOnlyHint=true, so the description does not need to restate that. The addition 'not sensitive-gated' provides a useful access-control detail beyond annotations, but other behavioral aspects such as pagination behavior, search semantics, and result shape are left undisclosed.

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 a single efficient sentence with no filler or redundant restatement of the schema. It front-loads the core purpose, though the parenthetical is somewhat jargon-heavy and could have been used to convey more high-value parameter or usage context.

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 search tool with four undocumented optional parameters and no output schema, one sentence is far too little. The description does not explain how finder works, what data is returned, how pagination behaves, or how payroll element entries relate to other payroll resources.

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% and the tool description adds no parameter-level meaning. q, limit, and offset are mildly inferable from their names, but 'finder' is opaque and the description does nothing to explain how it interacts with q or what values are expected.

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 states a specific action (Search) and a concrete resource (payroll element entries), which is clear and distinguishes it from related search tools like search_payslips or search_payroll_relationships. The 'read-only specialist' phrasing reinforces the lookup nature, though it partially restates the tool name.

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?

No guidance is provided about when to choose this tool over other payroll/search tools, and no exclusions or alternatives are named. The read-only hint and 'specialist' label imply a narrow query tool, but the description never states the conditions under which this tool should or should not be used.

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