Get Vacancy Details

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

No annotations are provided, and the description only states the operation. It does not disclose behavioral traits such as authentication requirements, rate limits, or whether it returns full details (e.g., includes description, contacts). Minimal disclosure beyond the basic action.

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?

Two sentences with no waste. The first sentence states the purpose clearly. The second provides parameter details in a structured format. Could be slightly improved with bullet points, but efficient overall.

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 tool is simple (one parameter) and has an output schema, so the description need not detail return values. However, it lacks context about prerequisites (e.g., authentication) and when to use vs. siblings. Adequate but with gaps.

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 schema has no description on the vacancy_id parameter (0% coverage). The description adds an example ('12345678') and clarifies it's an hh.ru vacancy ID, providing format and platform-specific context that aids correct invocation.

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 explicitly states 'Get full details of a specific vacancy,' using a specific verb and resource. This clearly distinguishes it from siblings like search_vacancies (listing) and apply_to_vacancy (action).

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?

Usage is implied: when you have a vacancy ID and need full details. However, no explicit guidance on when not to use or alternatives like search_vacancies for initial discovery. No prerequisites or context are mentioned.

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