Search live UK roles

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

With no annotations, the description must disclose behavioral traits. It does: it states the auth requirement (REED_API_KEY), explains the funnel output (showing what each filter removed so a small result set is understandable), and notes the exclusion logic. These go beyond the schema and help the agent anticipate how the tool behaves. It lacks details on error handling or rate limits, but core behaviors are covered.

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 two sentences. The first sentence states the core purpose and exclusions; the second explains the funnel and the auth requirement. No wasted words. The information is front-loaded: an agent gets the gist immediately, then the important behavioral details. This is exemplary conciseness.

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?

Given there is no output schema, the description explains the return format (a funnel) and the API key requirement. The parameters are fully documented elsewhere. The only minor gap is the precise structure of the funnel output, but that is not essential for calling the tool correctly. The description covers the key operational aspects an agent needs.

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?

All five parameters are fully described in the input schema (coverage 100%), so the baseline is 3. The description does not add parameter-specific guidance beyond what the schema provides; it mentions the funnel generally but doesn't tie specific parameters to outcomes. Since the schema already handles semantics, there is no deficit requiring compensation.

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 opens with a specific verb-resource pair ('Search live UK job listings via Reed') and adds a key scoping detail: exclusions of recruitment agencies and job boards, with the reason they cannot sponsor. This distinguishes it from sibling tools (check_sponsor, screen_posting, application_history) whose purposes are plainly different. An agent can tell exactly what this tool does and for whom.

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 gives context: it searches live UK roles on Reed and excludes entities that can't sponsor, implying it is used to find roles that can sponsor visas. It also explains the funnel output, which helps an agent interpret results. However, it doesn't explicitly state when to prefer this over siblings or when not to use it, though the tool names make alternatives obvious. The use case is well implied, if not formally stated.

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