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 mentions the behavior of returning empty list with no filters, but does not explicitly state that it is read-only or idempotent. However, the overall behavior is clear.

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?

Extremely concise: three sentences covering purpose, filter logic, valid values, date format, and a helpful tip. No wasted words, front-loaded with the tool's purpose.

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 11 parameters and no annotations, the description covers filtering logic, valid values, date format, and a cross-reference to list_users. The output schema exists, so return values are documented elsewhere. The description is complete for a search tool.

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. It lists all main filter categories (status, name, location, company, date range, owner) and mentions limit presumably. However, it does not describe individual parameters like city and country separately, and does not mention default values like limit=20. Still, provides sufficient understanding.

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 'Search for jobs' which clearly states the verb and resource. It lists specific filter fields (status, name, location, company, date range, owner), distinguishing it from sibling search tools like search_candidates and search_companies.

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?

Provides explicit guidance: filters are optional and combined with AND logic, status labels are enumerated, date format is specified, and suggests using list_users for valid owner_id. Also warns that with no filters, returns an empty list, setting proper expectations.

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