Get n8n Credential

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

The description goes beyond the annotations by explicitly stating that secret data is NOT returned, which is a key behavioral restriction not evident from readOnlyHint or idempotentHint. It also specifies 'metadata', clarifying the return type as non-sensitive information. The annotations already cover safety, so this added context earns a 4.

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 short and front-loaded with the main action and the critical secret-data warning. The Args block is redundant with the schema, adding minor noise, but overall it remains efficient and skimmable.

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?

For a simple get-by-ID tool, the description plus annotations provide sufficient context: read-only, idempotent, non-destructive, and returns metadata rather than secrets. It lacks detail on the exact metadata fields or possible errors, but given the schema and minimal complexity, this is acceptable.

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?

The only parameter 'id' is fully described in the schema with the same explanation ('Credential ID'). The description's Args section repeats the schema without adding new meaning (e.g., format, source, or validation). With 100% schema coverage, the description adds no extra parameter semantics.

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 a specific action ('Retrieve credential metadata by ID') and the resource. The 'Secret data is NOT returned' caveat further distinguishes it from other credential-related tools like n8n_get_credential_schema or n8n_create_credential.

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 implies usage when you need credential metadata by ID and notes that secret data is not available. However, it does not explicitly name alternatives (e.g., n8n_list_credentials for listing, n8n_get_credential_schema for schema) or provide exclusion criteria beyond the secret warning.

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