Screen a job posting

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose what the tool evaluates (the explicit criteria list), which is genuinely useful context. But it never states whether the call is read-only, what it returns, or any side effects — for an analysis tool with zero annotation coverage these gaps are felt.

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 a tight two sentences with no filler and front-loads the core purpose and criteria. The usage directive is placed at the end, which is acceptable given the value of the criteria list, though it could arguably lead with the 'run before applying' guidance for maximum salience.

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 two-parameter analysis tool with no output schema, the inputs are fully covered and the screening categories are spelled out. However, the description does not indicate what the result conveys — whether it returns a verdict, a risk score, or flagged bars — leaving an agent unsure what to expect from the 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 the schema already documents both title and description fully; this earns the baseline 3. The description adds marginal semantic value by signaling why the parameters matter (the analysis centers on the posting text), but does not add syntax or format detail beyond what the schema provides.

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 verb ('Screen') and resource ('a posting') with enumerated screening dimensions: hard eligibility bars (citizenship, residency, clearance, refusal to sponsor), hidden seniority, salary, and stack. This precise scope clearly differentiates it from siblings like check_sponsor, which covers only the sponsorship angle.

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?

'Run this before investing effort in an application' gives explicit timing and tells the agent to call it early in the workflow. However, it does not name alternatives or state exclusions — e.g., it never routes sponsorship-only cases to check_sponsor — so the guidance stops short of full alternative differentiation.

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