hent_roller

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action of retrieving roles without mentioning expected output format, error behavior, access requirements, or any side effects. This is minimal transparency, especially for a tool with no annotations.

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 that includes useful examples of roles and the target entity type. No redundant information, and it is front-loaded with the core action.

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?

As a simple single-parameter getter with no output schema or annotations, the description sufficiently conveys the tool's purpose and usage context. However, it would benefit from a note on what the returned roles actually represent or any limitations, but these are not critical for a straightforward retrieval tool.

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?

The input schema fully describes the single parameter as a '9-sifret organisasjonsnummer' (100% coverage). The description adds context by noting it applies to a 'norsk foretak', but this does not materially extend the parameter's meaning. Baseline 3 is appropriate given the schema covers the parameter well.

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 the specific verb 'Hent' (get) and resource 'roller' (roles) for a Norwegian enterprise, with examples of role types (board members, general manager, auditor). This clearly distinguishes it from sibling tools that handle enterprise search, enterprise details, subunit search, and subunit details.

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 usage when one needs roles for a specific enterprise, especially given the required 'organisasjonsnummer' parameter. However, it does not explicitly state when to use this tool instead of siblings, nor does it provide any exclusion criteria or alternatives.

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