list_jobs

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination, authorization requirements, or side effects. For a list tool, information about return volume or ordering is missing.

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 concise: two sentences plus parameter explanations. No superfluous information. However, the parameter docs are in a docstring format, which is slightly less structured but still clear.

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?

There is no output schema, and the description does not explain the return value format (e.g., list of job objects). With only two parameters and no authentication context, the description is insufficient for an agent to fully understand the tool's usage.

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%, but the description adds meaning: state is an optional filter with examples (Pending, Running, etc.), and top limits results. This partially compensates for the lack of schema metadata, though enum values are not fully listed.

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 'List jobs, optionally filtered by state.' This is a specific verb (list) and resource (jobs). It distinguishes from sibling tools like get_job (singular), start_job/stop_job (mutations), and list_robots/list_machines (other resources).

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 mentions optional filtering by state and parameter details, but does not explicitly state when to use this tool over alternatives (e.g., use get_job for a single job). No exclusions or when-not-to-use guidance is provided.

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