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 of behavioral disclosure. It establishes the source ('company career pages') and recency, but it does not mention any limitations, pagination behavior, staleness, or processing quirks. An agent is left to infer most behavioral expectations from the tool name and output schema.

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 two sentences with no waste. The purpose is front-loaded, and the parameter usage notes are compact and directly actionable.

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?

With five parameters, no annotations, and zero schema descriptions, the description is not complete enough for deliberate parameter selection. The output schema exists, so return values are covered, but key parameters like time_frame and description_format remain unexplained.

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%, so the description must compensate for all five parameters. It adds useful semantics for title and location, including OR syntax and full-name requirements, but it provides no guidance for limit, time_frame, or description_format beyond their default values.

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 states a specific verb and resource: 'Search recent job postings from company career pages.' It is clear about what the tool does, though there are no siblings to differentiate against, so it cannot earn the full 5 for sibling distinction.

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?

There is no alternative tool mentioned, but the description gives clear context: use this tool when searching recent job postings from company career pages. The OR-syntax and location-format notes also provide practical guidance for effective invocation.

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