Search Jobs

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says 'open job postings.' It does not disclose that the tool queries multiple external portals, whether results are aggregated or deduplicated, authentication requirements, rate limits, or error behavior across portals.

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 front-loaded sentence with no wasted words. However, its extreme brevity borders on under-specification rather than optimal conciseness for a multi-portal search tool.

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?

The tool has six parameters, queries multiple named job portals, and has an output schema, but the description does not mention multi-portal behavior, result aggregation, or freshness semantics. While the schema and output schema carry substantial detail, the description leaves key operational context unstated.

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 the schema already explains all six parameters, including portal options, limit per portal, and max_age_days. The description adds no additional parameter meaning, which is acceptable given the baseline for full schema coverage.

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 and resource: 'Search open job postings.' This distinguishes it from sibling tools like get_job_details or evaluate_job_fit, but it does not explicitly mention those alternatives or clarify the boundary between searching and retrieving details.

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 gives no guidance on when to use this tool versus alternatives. It merely restates the purpose, leaving the agent to infer that this is the entry point for job discovery before using get_job_details or evaluate_job_fit.

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