List n8n Credentials

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds crucial behavioral details: secrets are not returned, only metadata, and pagination is supported. It also mentions the role requirement. No contradictions with annotations.

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 succinct and well-structured with a title sentence, role/behavior note, and an Args list. The Args section is slightly redundant with the schema but remains readable and compact.

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 covers the essential context: credential listing is metadata-only, requires admin, supports filtering and pagination. It does not describe the return structure but that is not critical for this simple list tool.

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 67% (name and cursor have descriptions, limit has constraints). The description repeats the parameter list without adding new meaning beyond the schema, except for clarifying limit range and defaults which are already in the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 'List all credentials' with the specific scope of metadata-only results, distinguishing it from sibling tools like n8n_get_credential (single credential) and n8n_create_credential (write operation). The title and name reinforce the resource and action.

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 clear context for usage by requiring owner/admin role and explicitly warning that secrets are not returned. This indirectly guides the agent away from using this tool when secrets are needed. It does not explicitly name alternatives but gives sufficient contextual guidance.

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