n8n_find_workflows_using_credential

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

The description discloses key behaviors beyond what annotations would cover: 'Read-only. Bounded-concurrency fan-out; per-workflow fetch errors land in fetchErrors instead of failing the whole scan.' It also explains the return structure. Given no annotations, this fully informs the agent of the tool's operational characteristics.

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 well-structured and front-loaded with the main purpose. It is slightly verbose but every sentence adds necessary information. Could be trimmed slightly, but remains effective and clear.

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?

Despite lacking an output schema, the description thoroughly explains the return format: 'one finding per (workflowId, nodeName, credentialType) plus a per-workflow summary count.' It also accounts for error handling. Given the tool's complexity with 6 parameters, this is comprehensively complete.

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 description coverage is 100%, but the description adds significant value by explaining the interplay between parameters (e.g., credentialId vs credentialName) and clarifying defaults and behaviors for maxWorkflows and concurrency. For instance, it explains how maxWorkflows is counted and that concurrency has a default of 3.

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: 'Scan workflows and surface every node that references a given credential.' It also distinguishes itself from siblings by noting it 'Pairs with n8n_run_audit and is the answer to... before calling n8n_delete_credential.' This specificity helps the agent differentiate from other tools like n8n_find_workflows_using_node_type.

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 guidance on when to use the tool, instructing to pass either credentialId (preferred) or credentialName. It contextualizes usage: 'before calling n8n_delete_credential.' While it does not explicitly state when not to use it, the guidance is sufficient for correct invocation.

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