n8n: Get credential schema

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description contributes that the result enumerates required fields, which is genuinely useful behavioral context, but it says nothing about what else the schema returns or whether the lookup can fail for unknown credential types.

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 short sentences, front-loaded with the purpose. The unexplained '[UNIFIED]' tag is the only wasted token, so the text is otherwise efficient and easy to scan.

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 two-parameter read tool with no output schema, the description covers the basic job. It is still incomplete on the ambiguity that matters most here: the meaning of the required 'site' parameter and what a returned schema structure contains.

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 0%, so neither parameter is documented anywhere. 'credential_type' is largely self-explanatory from its name, but 'site' gets no explanation at all — the agent cannot tell whether it is an instance URL, an alias, or something else — and the description does nothing to fill that gap.

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 states a specific verb and resource — getting the schema for a credential type — and adds that it shows required fields, which distinguishes it in spirit from n8n_get_credential, which fetches an actual credential. It does not explicitly name that sibling, and the '[UNIFIED]' prefix is unexplained noise, but the core purpose is clear.

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?

There is no explicit when-to-use guidance, no mention of when to call this instead of n8n_get_credential, and no statement of prerequisites. 'Shows required fields' only weakly implies a discovery use case before creating a credential; the agent must infer the rest.

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