list_vacancy_applicants

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

The description provides no information about side effects, pagination, filtering, or output format. With no annotations, this leaves the agent uninformed about behavioral aspects.

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 extremely brief, consisting of a single noun phrase. While concise, it lacks essential verbs and clarifiers, making it under-informative rather than effectively concise.

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 fails to mention that the tool supports pagination (page, count), filtering by status, and raw output. Given the tool's moderate complexity, this information is necessary for correct usage, and its absence makes the description incomplete.

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 descriptions cover all six parameters with clear definitions. The tool description adds no additional context about parameters, so it neither improves nor detracts from the schema coverage.

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 'Candidates attached to a specific vacancy' identifies the resource (candidates) and scope (vacancy) but does not explicitly state the action (list/get). This makes it somewhat clear but relies on the tool name to infer the operation.

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?

No guidance is provided on when to use this tool versus alternatives like search_applicants. The description lacks any conditional usage instructions.

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