Evaluate Jobs

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

No annotations provided; description discloses the scoring behavior, range usage, and return type ('Returns text'). However, does not explicitly state if it modifies state or requires permissions.

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?

Moderate length but well-structured with clear instructions, front-loaded purpose, and every sentence adds value. Slightly wordy but necessary for complex scoring guidelines.

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?

Covers the scoring criteria, calibration, and post-call step. Lacks explicit return format details, but overall complete given the complexity and no output schema.

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 coverage is 100% with good field descriptions. Description adds contextual meaning about scoring logic, calibration, and post-call actions, going beyond schema details.

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?

Clearly states it scores one or more sourced jobs for a candidate, assigning 0-100 fit scores. Distinct from siblings like find_jobs (finding) and show_board (displaying).

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?

Explicitly says to use after finding jobs ('sourced jobs'), instructs to score all jobs in one call, and recommends calling show_board afterward. Also provides calibration advice.

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