Search Jobs

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds valuable context beyond annotations by specifying the return type (job_ids) and its intended use with get_job_details, which helps an agent understand the tool's role in a larger workflow.

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 only two sentences, front-loaded with the primary purpose ('Search for jobs on LinkedIn') followed immediately by the critical output detail. Every word serves a purpose with no redundancy or fluff.

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?

Despite having 9 parameters, the schema exhaustively documents them, and the output schema handles return values. The description explains the tool's overall purpose and the practical next step (passing job_ids to get_job_details), making it complete for an agent to invoke 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?

The input schema has 100% description coverage for all 9 parameters, so the schema already provides full parameter semantics. The description does not add any parameter-level detail, but the baseline of 3 is appropriate when the schema does the heavy lifting.

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 clearly states 'Search for jobs on LinkedIn' with a specific verb and resource, distinguishing it from sibling search tools like search_people and search_companies. It also adds unique value by explaining the return type ('Returns job_ids') and suggests a downstream workflow via get_job_details.

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 clear context: use this tool to search for jobs and receive job IDs for further detail retrieval via get_job_details. It does not explicitly state exclusions or alternatives, but the job-specific scope is obvious given the tool name and sibling context, so the implied usage is strong.

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