get_departments

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

The description discloses that the tool is for reference data, free, and uses no credits, which are important behavioral traits. As there are no annotations, this information adds transparency and sets correct expectations about cost and side effects (none).

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 concise sentence that conveys purpose, usage, and cost. Every word earns its place with no redundancy or fluff.

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?

Given the simplicity of the tool (no parameters, no output schema), the description fully covers what the tool does and why it would be used. It is complete for its intended purpose of providing reference data for filters.

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?

There are no parameters, so the input schema is fully covered. The description adds meaning by explaining the data's purpose and context, which is especially helpful for a parameterless tool.

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 explicitly states it provides department title codes for use as filter values in people searches, with a clear verb ('get') and resource ('all department title codes'). It distinguishes from siblings like 'get_department_functions' by specifying 'title codes'.

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?

It clearly indicates the tool is for retrieving filter values for people searches, with a note that it's free and uses no credits. However, it does not explicitly exclude other uses or compare with alternatives, though the purpose is clear enough.

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