set_department

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

With no annotations provided, the description carries the full behavioral burden, and it delivers: it explains comma-separated keyword matching, case-insensitive word-start matching, OR semantics across keywords, and that an empty string clears the default. It also uses 'save' and 'go back to searching every department' to disclose the persistent state change.

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 front-loaded with the core purpose and then expands into matching semantics, examples, and parameter details. Each sentence adds necessary information for correct use, and the structure is easy to scan despite the length.

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?

The description covers purpose, parameter syntax, matching behavior, edge cases, and clearing behavior. Since an output schema is present and the tool has only one simple parameter, nothing essential is missing for an agent to invoke it correctly.

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 0%, but the description fully compensates by explaining the single department parameter in depth: how to pass multiple keywords, how matching works, examples, and the special empty-string clearing behavior. This far exceeds the bare schema definition.

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 action: 'Set the default department or keyword used when searching and iterating.' This clearly identifies the resource (the saved filter) and the verb (set), and the tool is readily distinguishable from sibling tools like list_jobs and get_job.

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 states the tool affects searching and iterating, giving clear context for when it applies. It does not explicitly name alternative tools or conditionally exclude them, but the usage context is strong enough for an agent to infer when to call this setter versus listing or fetching jobs.

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