List Jobs

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

Annotations already declare readOnlyHint=true, so the safe-read nature is known. The description adds useful behavioral details: the REST endpoint, cursor-based pagination, and ordering by created_datetime descending. It does not contradict the annotations.

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, compact sentence that front-loads the endpoint and resource. It includes the most important information without unnecessary verbosity.

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?

For a read-only list tool with good annotations and full schema coverage, the description covers the essential behavior: endpoint, filtering, pagination, and ordering. It does not describe the return format, but this is inferable for a list operation and no output schema exists. The gap is minor.

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 all parameters are already documented in the schema. The description mentions status/type filtering and pagination, but these are also covered by the schema descriptions. No additional parameter meaning is added beyond the 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?

The description clearly states 'GET /api/jobs — List all jobs', identifying the resource and operation with a specific verb. It also mentions optional filtering and pagination, which distinguishes it from sibling tools like gorgias_get_job (single job) and gorgias_create_job.

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 conveys that this tool is for listing jobs, with filtering by status/type, which implies its use case. It does not explicitly exclude alternatives, but the list semantics are clear enough to guide selection. No explicit 'use when' or 'use instead' is given, so it falls short of a 5.

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