n8n_execution_stats

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

Declares itself 'composed read-only', explains pagination against /executions, mentions best-effort pagination and truncation. No annotations present, so description handles transparency well.

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?

Concise two-sentence core, followed by usage phrase and pagination note. No wasted words; front-loaded with purpose.

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?

Covers parameters, usage, behavior, and limitations. Lacks output format details (e.g., map per workflow), but acceptable for an aggregation tool without output schema.

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?

Adds context beyond schema: workflowId optional for per-instance stats, sinceHours window stops pagination, maxExecutions with truncation hint, pageSize default. Schema coverage is 100%, but description enriches understanding.

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 'Aggregate execution stats over a recent window' and lists computed fields (counts, failure rate, runtimes, timestamps). It distinguishes from siblings like n8n_list_executions by focusing on aggregation.

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?

Provides practical use cases ('which workflows are flaky?') and pagination advice ('if truncated: true, increase maxExecutions or narrow sinceHours'). However, it does not explicitly contrast with alternatives like n8n_search_executions.

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