hs_search_jobs

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

No annotations provided, so the description carries full burden. It lists returned fields but does not disclose behavioral aspects like authentication requirements, rate limits, or side effects (though it's read-only). The schema covers parameters well, but the description could add more about pagination behavior or result ordering.

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?

Exemplary conciseness: 3 sentences with zero wasted words. First sentence states purpose; second lists key outputs; third gives next step. No redundancy with schema.

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?

For a search tool with 5 optional parameters and an output schema, the description is nearly complete. It covers purpose, key outputs, and linkage to a related tool. Minor gap: no mention of pagination behavior beyond schema (e.g., default page size). Output schema exists, so return values are documented elsewhere.

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 adds no extra meaning beyond the schema; it merely summarizes returned fields which are already in the output schema. No parameter usage examples or constraints beyond schema are provided.

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?

Clear verb-resource combination - 'Search for jobs and internships on Handshake' explicitly states what it does. Distinguishes from sibling tools by listing returned fields and directing to hs_get_job for details, which contrasts with hs_search_employers or hs_get_job.

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 a clear workflow hint: 'Pass the posting ID to hs_get_job for the full description.' However, it does not specify when to prefer this tool over alternatives like hs_search_employers or when not to use it.

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