search_jobs

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

No annotations are provided, so the description carries the full burden. It discloses that the tool searches multiple platforms and uses a role keyword with optional filters. However, it does not mention behavioral details such as data freshness, rate limits, or what happens if no results are found.

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 single, well-structured sentence that conveys all essential information without any extraneous words. It is front-loaded with the main action and specifies the platforms and filters.

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's simplicity (3 parameters, 100% schema coverage, no output schema, no nested objects), the description is complete enough. It explains what the tool does and on which platforms. However, it could briefly mention the return format or that results are blended from multiple boards.

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 100% coverage for all three parameters, so the baseline is 3. The description adds minimal value beyond the schema, merely stating that the tool uses a role keyword and optional filters. It does not elaborate on parameter constraints or formatting.

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 it searches for open job listings on three specific platforms (RemoteOK, We Work Remotely, Himalayas) using a role keyword and optional filters. The verb 'search' and resource 'open job listings' are explicit, and the tool is well-distinguished from sibling tools that focus on applying or generating letters.

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 implies usage for finding jobs based on keywords and filters. While it does not explicitly state when not to use or mention alternatives, the sibling tools are clearly different in purpose (e.g., auto_apply, generate_cover_letter), so the context is clear.

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