postifys_cq_list_tables

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

With no annotations provided, the description carries the behavioral burden. It discloses important prerequisites (server flag and entitlement) and implicitly signals a read-only listing operation. It could be more explicit about output format or error behavior, but for a zero-parameter list tool this is reasonably transparent.

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 and uses three short sentences without fluff. The main verb phrase 'List data tables' is placed last and could be front-loaded, but the overall structure is efficient and easy to scan.

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 simple zero-parameter list operation, the description provides the key context: what the tool belongs to, what prerequisites exist, and what action it performs. It does not describe return values, but given no output schema and the simplicity of the operation, the coverage is adequate.

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, so the schema already covers everything. The baseline of 4 applies because there are no parameters and no parameter documentation gap to compensate for.

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 names the resource (Postifys Content Queue) and the action ('List data tables'). It distinguishes this tool from sibling tools like list_jobs and list_items by focusing specifically on tables.

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 clear context: this is for the native Postifys scheduler, not n8n, and requires CONTENT_QUEUE_ENABLED plus publish entitlement. It does not explicitly call out alternative tools or when-not-to-use conditions, 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.