hcm_get_notification

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

The description matches the readOnlyHint annotation, so there is no contradiction. However, it adds no behavioral details beyond what the annotation already conveys, such as not-found behavior, response format, or any additional context about the operation.

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, focused sentence with no filler. The key action and target are presented immediately, making it easy for an agent to parse and act on.

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-parameter, read-only get operation, the description combined with the schema and readOnlyHint is sufficiently complete for basic invocation. It could optionally mention how to discover notification IDs via hcm_list_notifications or describe the return shape, but the low complexity and lack of an output schema make those omissions acceptable.

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%, so the description must compensate. It does clarify that notificationId can refer to a task/notification id, which adds some meaning beyond the bare schema. However, it does not explain the expected format, source, or possible difference between task and notification IDs.

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 clearly states the verb 'Get' and a specific resource ('business process notification') identified by ID. It naturally distinguishes this tool from hcm_list_notifications by focusing on a single record fetch rather than a list operation.

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?

The description implies the tool should be used when a specific notification ID is available, but it does not explicitly state when to use it versus alternatives like hcm_list_notifications. No exclusions or pitfalls are mentioned, but the guidance is largely implicit.

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