hcm_get_national_identifier

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

The readOnlyHint annotation already signals a read operation. The 'SENSITIVE gate' warning adds useful context about restricted access, but it does not explain what the gate entails, such as permissions, denial behavior, or payload restrictions.

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 extremely short and front-loaded with no filler. However, 'SENSITIVE gate.' is a fragment, and the brevity leaves important context underspecified rather than being a clean, complete summary.

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 one-parameter getter, the description is minimal but incomplete. It omits the relationship to hcm_search_national_identifiers, the meaning of the sensitive gate, and what happens on unauthorized or missing-identifier requests.

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 adds no parameter-specific meaning. The parameter name nationalIdentifierId is self-explanatory as an identifier, but there is no guidance on format, how to obtain it, or how it maps to search results.

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 clear verb and resource ('Get national identifier') and the schema confirms a fetch-by-ID operation. It is distinguishable from hcm_search_national_identifiers by singular 'get' wording, though it does not explicitly name that distinction.

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: the caller must already have a nationalIdentifierId. It gives no explicit alternative or condition, even though hcm_search_national_identifiers is the obvious sibling for finding identifiers.

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