search_jobs

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

No annotations are provided, but 'Search' conveys a read-only operation and the description adds a useful result detail about direct apply URLs. It does not disclose pagination, rate limits, or potential dependence on external sources, but the behavior is not misleading.

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 three short sentences, front-loaded with the core purpose and followed by compact usage examples. Every sentence adds value and there is no filler.

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?

The presence of an output schema reduces the need to describe return values, and the description covers the main search terms well. However, it lacks details about optional parameters (limit, remote_only) and does not address the sibling tool, leaving minor gaps.

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 schema has four parameters with 0% description coverage. The description explains the query and location parameters with examples, but omits limit and remote_only, leaving two parameters underspecified. This is only partial compensation for the lack of schema 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 opens with 'Search current job listings,' which clearly specifies a search verb and the target resource. It does not explicitly contrast with the sibling tool job_search_sources, but the phrase 'current job listings' distinguishes the core function.

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 parameter usage examples ('use query for skills, titles, or companies') but does not state when to prefer this tool over alternatives or provide exclusions. There is no mention of when job_search_sources should be used instead.

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