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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely useful behavior beyond that: results are a mix of Instead-hosted and external independent listings, every job shows pay, and external applications go through the employer's site or a shared leave_details_url. It stops short of disclosing result limits, ordering rules, or pagination.

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 two-sentence block is a single promotional run-on, front-loaded with the resource (good) but padded with applicant-experience copy ('applying takes about two minutes from a phone with no account... within 48 hours') that does not help an agent select or call the tool. The operational content — the external-listing branch and leave_details_url — is buried at the end.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it does the most important part: results are heterogeneous (Instead listings vs. places hiring on their own sites vs. new UK places), with different follow-up actions for each. Missing result-count/pagination behavior keeps it from a 5, but it is sufficient to call correctly.

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% and all three filters (area, query, min_hourly_pay) are documented with examples in the schema, so the baseline is 3. The description adds no filtering or syntax detail of its own — notably it never mentions that the search can be narrowed by area, keyword, or pay, which is the tool's main invocation lever.

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 opening clause names the resource and scope precisely ('Live jobs at independent UK cafés, pubs, restaurants, bars, shops and salons on Instead, London first'), which is more specific than the sibling names alone would allow. It does not use a clean verb-first phrasing, and the marketing tail dilutes the signal, but an agent can still distinguish it from get_job and post_job.

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 description implies usage (browse/search listings, then apply on-site or at leave_details_url) but never states when to pick this over get_job or pay_rates. There are no explicit exclusions or preconditions (e.g. 'use get_job once you have an id'), so routing must be inferred from the tool name.

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