Get Recommended Vacancies

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

With no annotations, description carries full burden. Discloses use of matching algorithm, page loading, vacancies per page, and parameter defaults/range. Does not mention side effects (read-only), rate limits, or error handling for invalid resume_id.

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?

Concise paragraph followed by Args block. Good front-loading of purpose. Minor formatting improvement possible (e.g., bullet points), but overall efficient.

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 2 parameters, no annotations, and output schema, the description covers purpose, algorithm, parameters, and expected behavior. Complete enough for a read operation.

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 has 0% description coverage, so description adds significant value: explains resume_id sources (from get_my_resumes) with example, and max_pages with range, default, and per-page count.

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?

Clearly states the verb 'get' and resource 'recommended vacancies' with qualification 'for a specific resume'. Distinguishes from siblings like search_vacancies (general) and get_vacancy_details (specific).

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?

Explains that it uses hh.ru's matching algorithm and is equivalent to the 'Подходящие вакансии' page. Notes prerequisite resume_id from get_my_resumes. However, does not explicitly state when to use vs alternatives like search_vacancies.

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