List data tables

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

The description indicates a read-only list operation with optional features. No annotations are provided, so the description carries full burden; it could be improved by mentioning pagination behavior (cursor) or that it returns a list.

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?

Single sentence, no wasted words. Every part is relevant.

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?

Given the presence of an output schema, the description does not need to explain return values. It covers the key features (filtering, sorting, pagination) for a list tool, but could mention that cursor enables pagination.

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 coverage is 50% (filter and sortBy have descriptions, limit and cursor do not). The description names the optional features but does not explain parameter formats (e.g., JSON for filter, field:order for sortBy) beyond what is in 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 uses a specific verb ('List') and resource ('data tables'), and clearly distinguishes from sibling tools like n8n_get_datatable (single table) and n8n_create_datatable (create).

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, sorting, and pagination, implying usage when browsing tables. However, it does not explicitly contrast with sibling tools or state when not to use it.

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