n8n_get_credential_schema

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

With no annotations provided, the description carries the full burden. It adds the useful behavioral detail that the schema specifically 'Shows required fields,' indicating the output distinguishes mandatory vs optional fields. However, it lacks disclosure on whether this is a read-only operation, response format, or caching behavior.

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 appropriately brief at two sentences. However, the '[UNIFIED]' prefix appears to be implementation metadata rather than descriptive content, slightly diluting the information density without adding value for tool selection.

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 tool with two simple parameters and no output schema, the description captures the core retrieval purpose. However, given the complete lack of schema documentation for parameters, the description is minimally viable but incomplete—it should explain the parameter semantics to be fully adequate.

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 input schema has 0% description coverage for both 'site' and 'credential_type' parameters. The description completely fails to compensate for this gap by explaining what constitutes a valid site identifier or credential_type value, leaving critical parameters undocumented.

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 'Get[s] the schema for a credential type' with the specific behavioral detail that it 'Shows required fields.' While the '[UNIFIED]' prefix is unnecessary metadata noise, the core purpose is unambiguous and distinguishes from sibling n8n_get_credential (which retrieves credential instances, not schemas).

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?

No guidance provided on when to use this tool versus siblings like n8n_get_credential or n8n_create_credential. No mention of prerequisites (e.g., needing to know valid credential_type values beforehand) or when this schema retrieval is necessary in a workflow.

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