search_jobs

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

With no annotations, the description must disclose behavior. It notes empty filters are ignored and returns job records, but omits details like pagination, sorting, rate limits, auth requirements, or side effects. This is insufficient for an 8-parameter tool.

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 short and front-loaded, but it omits critical information. While concise, it sacrifices completeness for brevity, earning a middle score.

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 output schema exists, returning values need not be explained. However, the description fails to cover 8 parameters with no schema descriptions, lacks usage guidance, and provides minimal behavioral context, making it incomplete for the tool's complexity.

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 explain parameter meaning. It only mentions that empty filters are ignored, providing no detail on what each of the 8 parameters (firm, limit, query, etc.) does. This leaves agents to guess from names alone.

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 the job database and returns job records. The verb 'Search' and resource 'job database' are specific, and it distinguishes from siblings like 'get_job' (single retrieval) and 'add_jobs' (creation).

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 mentions 'Empty filters are ignored,' which provides some usage context but does not specify when to use this tool versus alternatives like 'get_job' or 'archive_job'. No explicit when-not or alternative guidance.

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