get_employer_vacancies

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the auth profile ("No token required", "public") and that results are read-only listings of active vacancies. It says nothing about pagination behavior or return shape, which for an unannotated list tool is a real gap.

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 tight sentences with the core scope front-loaded and no filler. The token-free constraint is appended economically where it matters.

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?

With no annotations and no output schema, the description should do more work. It covers scope and auth adequately but omits handling of paging (page/per_page defaults) and what the compact summary versus raw JSON contains, leaving meaningful gaps for a 4-parameter listing tool.

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 four parameters (employer_id, page, per_page, raw) are already documented in the schema. The description reinforces that employer_id is the filtering key but adds no format, default, or paging semantics beyond the schema; 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?

States a specific verb and resource ("List active vacancies for a specific employer") and identifies the mechanism ("public vacancy search (employer_id filter)"). It implicitly separates itself from siblings like list_active_vacancies by signaling a public, employer-scoped search, but never names the sibling it should be chosen over.

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 phrase "via public vacancy search (employer_id filter). No token required." implies when this tool applies (unauthenticated, employer-scoped lookups) versus token-based siblings. However, it gives no explicit when-to-use/when-not-to-use instruction or named alternative, leaving the caller to infer the distinction.

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