Dict Professional Roles

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

With no annotations, the description carries the full burden: it implies a read-only lookup returning a hierarchical dictionary, which is baseline-appropriate. It says nothing about response size, caching, or whether the tree is complete, but for a zero-parameter dictionary lookup these omissions are minor.

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?

A single sentence, front-loaded with the verb and resource, followed by the returned structure and the downstream use of role ids. Dense and waste-free, though the semicolon clause is slightly compressed.

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 parameterless dictionary tool with no output schema, the description sketches the return shape (tree with sub-categories and numeric ids) and mentions how the ids are consumed. That is enough for an agent to select and call it, with only per-node field names left unspecified.

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 tool takes no parameters, so the baseline is 4. The description appropriately focuses on what the call returns rather than inventing parameter semantics that do not exist.

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 states a specific verb and resource (get the tree of professional roles) and clarifies the content: job categories, sub-categories, and their numeric ids. It is clear what the tool returns, though it does not explicitly distinguish itself from the sibling suggest_professional_roles.

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 gives an implied usage context by noting that role ids are used in vacancy and resume search. However, it does not say when to prefer this full dictionary over the autocomplete-style sibling suggest_professional_roles, leaving the choice to inference.

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