list_jobs_overview

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

No annotations provided. Description calls it a 'condensed overview' but fails to explain what fields are included, pagination behavior (page/limit), or how filters combine. For a tool with 14 optional parameters, more behavioral context is needed.

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?

Single sentence is concise but too vague to be helpful. Could be restructured to include key behaviors without significant lengthening, e.g., noting return format or filter semantics.

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 14 parameters, no annotations, and an output schema presumably describing return fields, the description is insufficient. Tool complexity demands explanation of common use cases or parameter interactions, which are entirely absent.

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 0%. The description only mentions 'filters' generically without describing any of the 14 parameters. Parameters like 'ids', 'state', 'result', etc., remain undocumented, forcing reliance on schema names alone. Description adds no value beyond schema.

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?

Description clearly states it lists a condensed jobs overview matching filters. 'Condensed' implies a summary view, distinguishing from sibling 'list_jobs' which likely returns full details. However, lacks explicit differentiation from other listing tools like 'find_jobs_by_setting'.

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 on when to use this tool versus siblings. With tools like 'list_jobs', 'get_job', 'find_jobs_by_setting', and 'list_jobs_overview', the description offers no context for selection, such as suggesting this tool for summaries or quick overviews.

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