hcm_search_talent_profiles

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

The readOnlyHint annotation already covers the safety profile, but the description adds no behavioral context beyond restating 'Search'. It does not mention result shape, pagination behavior, what 'talent person profile' means, or any constraints on the search, so there is little disclosure beyond what annotations already provide.

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 short sentence with no filler or redundant explanation. It is front-loaded and easy to parse, though it is arguably so terse that it sacrifices useful detail.

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 read-only search with three optional parameters, this is minimally adequate, but there are clear gaps: no differentiation from sibling search/get tools, no parameter semantics, and no indication of what the response contains despite there being no output schema. An agent could call it, but not with much confidence about results or filtering behavior.

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 description does not explain any of the three parameters. The names q, limit, and offset are somewhat self-explanatory, but 'q' is ambiguous and neither the schema nor the description defines search semantics, defaults, or required combinations.

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 uses a specific verb ('Search') and a resource ('talent person profiles'), so an agent can tell this is a list/query operation rather than a get/update/delete. It does not explicitly differentiate from hcm_search_workers or hcm_get_talent_profile, which prevents a 5, but it is not a tautology.

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 on when to choose this tool over siblings like hcm_get_talent_profile (retrieve a single profile) or hcm_search_workers (search worker records). The description leaves usage entirely to inference from the name, with no context about expected use cases or exclusions.

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