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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds the default sort order (newest first), which is genuinely useful, but says nothing about pagination behavior, result volume, or response shape beyond what the schema covers.

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 compact sentences plus an endpoint path, with the resource and sort order front-loaded. There is no filler, though the endpoint path is arguably redundant for an agent that already has the tool name.

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 simple, all-optional read-only list tool with full schema coverage and complete annotations, the description tells the agent enough to call it correctly. The only gap is the absence of an output schema paired with no note about what a job record contains, which is a minor shortfall for a list endpoint.

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 six parameters are already documented (page, per_page, keyword searches alias or id, branch_ids, published_only, job_position_ids). The description merely paraphrases those filters and adds no syntax, combination rules, or format details; 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 resource ("Job openings of the company") plus ordering ("newest first") and the endpoint, so the agent knows this is a scoped list operation. It does not explicitly distinguish itself from the sibling talenta_get_job, which is the main thing keeping it below a 5.

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 only implied: the filter list (keyword, branch, job position, career-page-only) hints at when to reach for this tool, but there is no explicit "use this when..." or "for a single job use talenta_get_job instead". An agent must infer the boundary from the tool name alone.

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