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

The annotations already carry readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds scale ('1M+ listings from 20K+ companies') and indicates the breadth of filtering, but it does not disclose behavioral caveats such as semantic search being limited to remote+tech jobs or the list/pagination nature of the result. Since there is no contradiction with the annotations, a 3 is appropriate.

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 tight two sentences, front-loaded with the core action and scale. The second sentence lists capability areas but stops short of explaining selection logic; this is still economical, though the sentence could have been replaced with sibling-routing guidance for even better value.

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?

A 16-parameter tool with no output schema could use a bit more orientation: the description doesn't mention that all parameters are optional, recommend a query/vs filter-based strategy, or point to siblings for filter options and single-job detail. However, the schema is rich and the tool is a read-only listing endpoint, so the definition is at the 'minimum viable' level rather than clearly lacking.

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 81%, so the schema already documents most parameters. The description names query, semantic query, location, salary, remote type, seniority, and skills—none of which adds meaning beyond the param-level texts; it just restates their categories. Baseline 3 applies because the coverage is high.

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 names a specific verb and resource: 'Search 1M+ job listings', and immediately enumerates the major capabilities (keyword/semantic search, filters). It is clear enough that an agent can tell this is a job-list retrieval tool, but it does not explicitly contrast against the sibling tools (e.g., get_job, find_similar_jobs), leaving some differentiation to inference.

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?

No guidance is given about when to use this tool versus the siblings get_job, find_similar_jobs, get_filter_options, or get_company. There is no statement of when-not-to-use, no prerequisite, and no pointer such as 'use get_filter_options for valid values'. The usage is only inferred from the name and general-purpose search description.

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