search_jobs

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

With no annotations, the description must reveal behavioral traits. It states the tool returns 'open positions, status, and the assigned recruiter', but does not mention pagination behavior (page, per_page) despite the schema including those parameters. This is a notable gap in transparency.

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 extremely concise with two sentences: one stating the purpose, the other providing an alternative usage. Every word serves a purpose, no 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?

Given the tool has 7 parameters and an output schema, the description is insufficient. It mentions what is returned (open positions, status, recruiter) but omits how to filter (keyword, location, etc.) and pagination details. Users would need extra documentation to use the tool effectively.

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 0%, yet the description adds no information about individual parameters. The tool has 7 parameters (keyword, location, status, etc.) but the description only says 'Search job openings', leaving their meanings entirely inferred. This fails to compensate for the schema's lack of descriptions.

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 starts with a clear verb+resource: 'Search job openings', specifying the tool's primary function. It distinguishes itself from sibling tool get_job_pipeline by directing users to use that tool for candidate pipeline needs, preventing confusion.

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 explicitly tells users when to use an alternative (get_job_pipeline for candidate pipeline), providing clear context. However, it does not address other siblings like search_candidates or create_job_opening, leaving some usage ambiguity.

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