postifys_cq_list_jobs

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context about native Postifys Content Queue, the required feature flag, publish entitlement, and the one-job-per-table constraint. However, it does not mention return format, pagination, or whether the operation is read-only, though listing implies it.

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 compact, front-loaded, and every sentence earns its place. It conveys functionality, prerequisites, and a key behavioral constraint in two short sentences with no filler.

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 zero-parameter list tool with no output schema, the description covers the essential invocation context: what the tool lists, the prerequisite flag and entitlement, and the one-job-per-table model. It could be slightly more complete by noting whether the list is ordered or paginated, but the low complexity makes this a minor gap.

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 tool has zero parameters and schema description coverage is 100%, so the schema already conveys the complete absence of parameters. The description does not need to explain parameters, and mentioning the 'one job per table' behavior adds useful semantic context beyond the empty 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 the tool's purpose: 'List publishing jobs (one job per table).' It uses a specific verb and resource and naturally distinguishes itself from sibling tools like cq_list_tables and cq_list_items by targeting 'jobs' at the table level.

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 provides actionable prerequisites: 'Requires CONTENT_QUEUE_ENABLED on the server and publish entitlement.' It gives clear context that this is the native Content Queue feature without n8n, but it does not explicitly name alternatives or state when to choose this over cq_list_tables or cq_overview.

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