hcm_get_payslip

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds 'SENSITIVE gate,' which hints that this operation may trigger additional access controls or approval steps, but it does not explain what the gate entails, leaving the behavioral context vague.

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: 'Get payslip by id' says the core action, and 'SENSITIVE gate' adds a relevant caution. No words are wasted, though the terseness leaves room for more useful information.

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 tool with no output schema and a sensitive-data annotation, the description is too sparse. It does not clarify what the sensitive gate does, what authorization is required, or how the returned payslip data is structured, so an agent may not know the implications of calling it.

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 for the undocumented payslipId parameter. It only restates 'by id' without clarifying the ID format, source, or whether this is an Oracle HCM payslip ID versus another identifier, so it adds little beyond the property name.

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 a specific verb ('Get') and resource ('payslip by id'), so an agent can tell this is a direct fetch operation. However, it does not explicitly distinguish itself from the sibling hcm_search_payslips, so it misses the full differentiation expected for 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?

There is no guidance on when to use this tool versus hcm_search_payslips or other related getters. The phrase 'by id' implies direct lookup, but it never states that search should be used when the payslip ID is not already known, nor does it mention any exclusions.

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