n8n_get_credential

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns 'metadata' (implying not full secrets/values) and notes the API limitation regarding listing. However, it omits read-only status, authentication requirements, error behaviors, and return structure.

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 information front-loaded. The '[UNIFIED]' tag is structural cruft, but the remainder is efficient. The note about API limitations earns its place by preventing misuse.

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?

Adequate for a simple 2-parameter getter tool, clarifying the metadata scope of the return value. However, with no output schema provided, the description could better describe the return structure. Parameter documentation gap limits completeness.

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 0%, requiring the description to compensate. While 'by ID' implicitly references credential_id, the description fails to explain the 'site' parameter or provide format details for either parameter. Partial compensation only.

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?

States specific action (Get) and resource (credential metadata) with scope (by ID). The '[UNIFIED]' prefix is noise, but the core description is clear. Distinguishes intent from sibling n8n_get_credential_schema by specifying 'metadata' rather than schema/type information.

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 a negative constraint ('Listing all credentials is not supported') which implies this tool requires a specific ID and cannot be used for broad enumeration. However, lacks explicit when-to-use guidance versus alternatives like n8n_get_credential_schema or n8n_create_credential.

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