hcm_get_compensation

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

The readOnlyHint annotation already covers the read-only nature. The description adds 'SENSITIVE gate', which signals access sensitivity, but gives no detail about what the gate entails or what behavior the agent should expect beyond the annotation.

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, but it is terse to the point of under-specification. 'SENSITIVE gate' is attention-grabbing but adds a warning without explanation, so the brevity does not fully earn its place.

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 sensitive compensation-data tool with no output schema and minimal description, an agent is left without important context such as what the response contains, what 'SENSITIVE gate' means operationally, or how compensationId should be obtained. The annotations cover read-only safety but not the gating 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 the meaning or format of compensationId beyond the schema's field name. The phrase 'compensation row' loosely implies the id identifies a row, but that adds little semantic value.

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 clear verb and resource: 'Get compensation row' indicates a fetch-by-identifier operation. It is broadly distinguishable from a search tool like hcm_search_compensation, though it does not explicitly contrast itself with that sibling.

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 given about when to use this tool versus alternatives such as hcm_search_compensation. The 'SENSITIVE gate' phrase hints at caution but does not explain when this tool should or should not be invoked.

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