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

Annotations already cover read-only and open-world behavior, and the description goes further by disclosing the returned field set, the absence of salary data, a 300-posting recency cap, and a per-call price with the 'failed calls are not charged' exception. The only blemish is tension between 'newest 300 postings' and the schema's limit of 1-50, which could confuse an agent about result volume.

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?

Front-loads the resource and source, then data characteristics, caveats, sibling routing, and price in a logical order. The sibling clauses are verbose ('when you need Open roles from one company's ... job board' repeated twice) and the pricing sentence is long, but every element carries actionable 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?

With an output schema present, the description needn't explain return values, yet it usefully summarizes fields and the missing salary column, and it uniquely covers cost and charging behavior. The unresolved 300-versus-50 result-size question is the main gap for an agent deciding what to expect from a call.

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 both parameters are already documented and the baseline applies. The description mentions remote roles generally but does not clarify the string-valued 'true' convention for remoteOnly or reconcile the 300-posting claim with the 1-50 limit range, adding little meaning beyond the schema.

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), the exact source (Arbeitnow public job board API), and the geographic/remote skew of the data. It also names the two most relevant siblings and what they cover instead, so an agent can distinguish this from other job-board tools without reading schemas.

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?

Gives explicit routing for two alternatives ('jobs_ashby_jobs_board when you need open roles from one company's public Ashby board' and the Greenhouse equivalent), and signals this is the broad Europe/remote aggregator. It does not address the other ~50 job-board siblings or say when this source is preferable to a larger aggregator, but the alternative guidance is concrete rather than implied.

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