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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds nothing further: no pagination behavior, no rate limits, no statement of what the feed returns or whether results are limited to currently open roles. For an open-world feed, this is thin.

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 short, front-loaded sentence with no filler. It is efficiently written but under-specified rather than truly concise — brevity here comes at the cost of missing information rather than from trimming redundancy.

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?

An output schema exists, so return values need not be described. Still, for a 4-parameter, 0%-coverage tool the description omits everything an agent needs beyond the source name: the action performed, filter semantics, and any behavioral constraints.

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 0% across 4 parameters, so the description must carry the burden and does not. Only the required 'company' parameter is obliquely referenced ('for a company'); the meaning and accepted values of remote, location, and department are left entirely unexplained.

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 names a specific resource (Personio job board feed) scoped to a company, which does distinguish it from the many other jobs_*_board siblings by source. However, it never states the action — 'feed' implies listing postings but no verb confirms it, leaving the operation implied rather than stated.

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 indication of when to use this tool versus the dozens of other job-board siblings (jobs_greenhouse_board, jobs_lever_postings, jobs_workable_postings, etc.), nor any prerequisites or exclusions. The agent must infer usage purely from the name.

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