hibob_get_company_named_lists

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral details: list_name is optional and None returns all lists, and the return value is a JSON mapping to IDs and display names. No contradiction with 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 compact and well-organized into Args, Returns, and Examples. Every sentence advances understanding, and the most important workflow context ('position fields must use named lists') 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 single-optional-parameter read-only lookup, the description provides purpose, usage timing, parameter behavior, return shape, and an example. Nothing needed for correct invocation is missing.

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%, so the schema fully documents list_name. The description adds value with concrete examples ('Which departments exist?' -> list_name='department') and by restating the None/omit semantics in plain language, going slightly beyond the schema baseline.

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 opens with a specific verb and resource: 'Look up the allowed values of HiBob's named lists.' It further clarifies that the tool resolves names to IDs used by hibob_create_position and hibob_update_position, making its distinct role among position-related siblings clear.

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 gives explicit context: position fields must come from named lists, and this tool should be used before creating or updating positions to convert names to list-item IDs. It does not mention when-not-to-use or contrast with an alternative lookup sibling, but none is apparent among the listed tools.

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