move_list_jobs

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

Annotations already declare readOnlyHint and openWorldHint. The description's extra claim about filtering to one take duplicates the schema description of take_id, and it does not disclose pagination, expansion, or sorting behavior. No contradictions, but no meaningful additional behavioral context.

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 concise sentence with the verb and object front-loaded. It contains no filler, though it is probably too terse to cover the tool's parameter-dependent behavior.

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?

Despite having five optional parameters and an output schema, the description only covers the basic list action and take filter. It omits pagination, expand options, and sorting, and does not reference the output schema or open-world behavior, leaving the agent to infer important context from 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 only 40%, so the description needed to explain first, expand, and sort_direction, but it only restates the take_id filter already documented in the schema. It adds no new meaning for the majority of parameters.

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') and resource ('jobs'), and adds a scoping condition ('optionally filtered to one take'). This distinguishes it from sibling move_get_job (single job fetch) and move_list_takes (different resource).

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 prefer this tool over alternatives such as move_get_job or move_list_takes. It implies usage only by naming the list operation, but does not state exclusions or conditions.

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