Suggest Professional Roles

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the prefix-matching behavior and that ids are returned alongside names, but says nothing about result caps, case sensitivity, language/locale selection, or whether an empty prefix is allowed.

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 front-loaded sentence with no filler; the matching mode and return value come before the use case. Slightly awkward phrasing ('with their ids for vacancy and resume search') but nothing is wasted.

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 one-parameter suggest tool with no output schema and no annotations, the description covers purpose and return shape but omits practical calling details such as result limits and locale behavior. Adequate, but an agent would likely need a trial call to learn the bounds.

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 description coverage is 0% and the lone 'text' parameter is undeclared in the schema. The phrase 'by name prefix' does tell the agent what to pass, which recovers some meaning, but format constraints (minimum length, casing, multiple words) remain undefined.

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?

States a specific verb (suggest) and resource (professional roles), plus the matching mode (name prefix) and the returned value (ids). It does not explicitly distinguish itself from the similarly-named sibling dict_professional_roles or suggest_positions, leaving the agent to infer dict-vs-suggest semantics.

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 clause 'for vacancy and resume search' implies the context in which this lookup is useful, which is better than nothing. However, no exclusion or alternative is named (e.g., 'use dict_professional_roles to list all roles'), so the agent must guess when a prefix suggest beats the full dictionary sibling.

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