nhcx_get_user_role

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates that the tool 'gets' role and allowed actions, but does not disclose side effects (e.g., read-only), authentication requirements, rate limits, or error behavior. The 'Always call' note is workflow guidance rather than behavioral transparency.

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 two sentences: one states the purpose, the other gives a clear directive. Every word earns its place, and the critical usage note is front-loaded.

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 2-parameter tool with no output schema, the description explains what is returned (role and allowed actions) and when to call it (before processing). It lacks mention of prerequisites like login, but the sibling list includes nhcx_login, and the core information is sufficient for most use cases.

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 coverage is 100% for both parameters, so the description adds little beyond the schema. The phrase 'for a case' maps to caseId, but no new meaning is added for payerId or the parameters in general. Baseline 3 is appropriate.

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 ('Get') and clearly identifies the resource ('current payer role for a case and the allowed actions for that role'). This distinguishes it from sibling tools like nhcx_login (auth) and nhcx_process_case (processing), making the tool's purpose unambiguous.

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 instruction 'Always call this before processing a case' provides clear context on when to use the tool relative to processing a case. However, it does not mention when not to use it or explicitly name alternatives, so it falls slightly short of a 5.

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