get_ai_jobs

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose pagination behavior (despite a 'limit' parameter), result freshness, data source, or any rate limits. For a search tool with zero annotation coverage, these gaps are significant.

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 efficient sentence with no waste, though it is so minimal that conciseness comes at the cost of content. It is appropriately front-loaded.

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?

An output schema exists, so the description needn't explain return values. However, for a search tool with three undocumented parameters (including a non-obvious 'remote' default) and no annotations, the description is incomplete—it should at minimum clarify parameter semantics and usage.

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%. The description provides no meaning for 'limit', 'remote' (which has a non-obvious default of -1), or 'company'. Because the schema itself is bare, the description should compensate but does not, leaving key semantics undocumented.

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 clear verb ('Search') and resource ('AI industry job postings'), which is more specific than most siblings in this set. However, it does not differentiate itself from siblings like get_company_intelligence, which could also surface hiring data, so it falls short of a 5.

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 says nothing about when to use this tool versus alternatives such as get_company_intelligence, nor does it state prerequisites like API keys or rate limits. No usage context is provided beyond the verb.

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