n8n_list_schedules

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

With no annotations, the description declares 'Read-only' and describes scanning behavior (scans recent workflows when workflowId omitted, defaults to active only). This adds value beyond the schema, though limitations like 'recent' are not precisely defined.

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?

Two sentences with the main purpose front-loaded. The second sentence is packed with detail but still efficient. No filler words, but could be slightly more concise.

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 no output schema, the description vaguely mentions returning 'workflow context + raw rule' but lacks specifics on data structure. It covers tool purpose and parameter usage well but omits return format details.

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 100% with clear descriptions for each parameter. The tool description does not add additional semantic details beyond what the schema already provides, so baseline score of 3 is appropriate.

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?

Description clearly states the tool surfaces schedule triggers across workflows, decodes interval rules, and returns workflow context. It distinguishes from sibling tools which focus on credentials, nodes, and executions, none of which list schedules.

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?

Description provides context ('answer what's running at 3am?') but does not explicitly state when to use vs alternatives or when not to use. There are no direct sibling competitors, so guidance is adequate but lacks exclusions.

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