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 discloses update frequency ('updated hourly'), result limit ('up to 10'), and output details (total match count, browse URL). It also clarifies that all apply flows go through the returned job URLs. This is sufficient behavioral context.

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 three concise sentences, each purposeful. First sentence states the core action, second summarizes output, third clarifies the apply flow. No redundant or irrelevant information.

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 no output schema, the description covers the key output elements (matching roles, total count, browse URL). It also includes update frequency and scope. It does not cover error handling or empty results, but for a search tool this is adequate.

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 100%, so baseline is 3. The description does not add new meaning beyond what the schema provides for any parameter. For example, the 'query' parameter description in the schema already states 'Free-text search over title/company/location'.

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 uses a specific verb 'Search' and a well-scoped resource 'live cybersecurity jobs from 200+ security companies'. It clearly distinguishes this tool from siblings like 'get_job' (single job) and analytical tools like 'market_stats'.

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 clearly states what the tool does and mentions it returns a browse URL for full results. However, it does not explicitly state when to use this tool versus alternatives, though the sibling context makes it somewhat clear.

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