search_hh_vacancies

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

With no annotations, the description carries the burden of disclosing behavior. It does disclose that the tool searches via an authenticated browser and filters results by a configured score threshold. However, it does not mention browser side effects, rate limits, authentication failure behavior, or whether the operation modifies any state.

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 sentence with no filler. It front-loads the core action and packs the two most important qualifiers—authenticated browser and score threshold—into a compact, readable form.

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 establishes the core purpose but is incomplete for safe and correct invocation. There are no annotations, no output schema, and no parameter semantics beyond types/constraints, so the agent cannot confidently know how to use `area` or `pageLimit`, what the result structure is, or what prerequisites must be met.

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%, so the description must compensate, but it does not explain any of the three parameters. The terms 'area' and 'pageLimit' are left entirely to the agent to infer, and 'query' is only implicitly connected to the search action.

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 clearly states the action ('Search HH.ru'), the execution context ('selected authenticated browser'), and the key filtering behavior ('only vacancies meeting the configured score threshold'). It is readily distinguishable from siblings like get_settings and set_min_score, which are configuration-oriented.

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 implies when to use the tool: when a search of HH.ru with score-based filtering is needed. It references the 'selected authenticated browser' and 'configured score threshold,' hinting that set_browser and set_min_score are prerequisites, though it does not explicitly name alternatives or exclusions.

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