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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description adds that results are reference entities carrying ids and names. It does not state result volume or that paging must be followed via next_page, which the schema handles for page/limit but not for the overall retrieval loop.

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 sentences, front-loaded with the verb and the resource, and the purpose sentence follows immediately. The 15-item enumeration is long and duplicates the schema enum, but it doubles as the primary selection aid, so the cost is largely justified.

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 simple single-enum lookup with no output schema, the description covers what the tool returns (ids and names) and why an agent would call it. Missing only the pagination contract and any note on how these lists relate to the entity-specific list siblings.

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?

The description re-enumerates the kind values already present in the schema enum, adding little beyond confirming they are reference-list names. page and limit semantics live entirely in the schema (67% coverage), and the description adds no guidance on how these lists are typically sized or paged.

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?

Specific verb ('Look up') plus resource ('intelliHR's reference lists') with a full enumeration of the kinds available, which lets an agent recognize it as the generic reference-data lookup. It does not disambiguate from conceptually overlapping siblings such as intellihr_list_skills, intellihr_list_qualifications or intellihr_list_position_titles, so a 4 rather than 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?

'Use it to find the ids and names other tools need' gives a clear, concrete usage context: resolve identifiers before calling create/update tools. There is no when-not guidance and no pointer for choosing between this tool and the entity-specific list siblings that may return the same data.

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