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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by naming the returned fields (role, company, city, salary, link), which compensates for the absent output schema, and by scoping results geographically. It still omits ordering and empty-result behavior, so it is not fully transparent.

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 compact sentence with the action, domain scope, and returned fields front-loaded. There is no redundant or filler wording; every clause carries information.

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 three-optional-parameter read tool with no output schema, the description is nearly sufficient: it names the result fields and the geographic/domain scope. The remaining gap is the lack of routing guidance against the sibling search_* tools, which matters since several similarly named search tools exist.

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 100%, so all three parameters (limit, query, location) are already documented with examples in the schema. The description merely echoes that city and role are relevant, adding no syntax, matching behavior, or format detail beyond what the schema provides; baseline 3 applies.

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 gives a specific verb ('Найти') and resource ('вакансии') and constrains the domain to AI/ML jobs in Russia, plus enumerates the returned fields (role, company, city, salary, link). It does not explicitly differentiate itself from siblings like search_models or search_subscriptions, though the resource noun makes the distinction reasonably inferable.

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?

There is no explicit when-to-use or when-not-to-use guidance, nor any mention of the sibling tools (search_models, search_subscriptions) as alternatives. Usage is only implied by the domain scoping 'в сфере ИИ и машинного обучения в России', which an agent can infer but must not be told directly.

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