list_new_jobs

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

No annotations are present, so the description carries the burden of disclosing side effects and context. It accurately describes the listing and sorting behavior but does not mention whether the tool modifies notification status, limits results, or requires authentication. The description adds the sorting detail but lacks depth on what 'un-notified' entails.

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?

Two short sentences convey the core purpose and parameters without wasted words. The information is front-loaded and easy to parse.

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 description covers the basic functionality but omits details like return format, pagination, or how this tool differs from similar list/search tools. Without an output schema or annotations, the description should provide more completeness, but for a simple listing tool it is minimally viable.

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?

The description labels domain and min_score as 'optional filters', providing some context beyond the bare schema (which has no descriptions). However, it does not clarify what domain values are allowed or how min_score scales, so semantic meaning remains partial. Given 0% schema coverage, more detail would be beneficial.

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 the action ('List'), the specific resource ('un-notified jobs'), and the sorting behavior ('sorted by score'). This distinguishes it from siblings like search_jobs and filter_jobs by focusing on the un-notified subset.

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 phrase 'un-notified jobs' implies the intended use case (retrieving jobs that haven't been notified), but there is no explicit guidance on when to choose this over alternatives like fetch_jobs or get_top_matches. No exclusions or alternative tool references are provided.

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