MCP Hub

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

No annotations provided, so description carries full burden. It discloses the commercial/licensing constraint but fails to explain pagination behavior (limit/cursor), rate limits, or what the return format looks like. No mention of variable scoping or visibility rules.

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?

Extremely concise at three sentences. Front-loaded with [UNIFIED] [Enterprise] context tags. However, brevity becomes a liability given zero schema documentation and the presence of pagination parameters that require explanation.

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?

Given 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is insufficient. It misses: pagination mechanics (limit/cursor interaction), required vs optional field clarification, return structure, and variable filtering capabilities.

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 has 0% description coverage. The description provides only one parameter claim ('All parameters are OPTIONAL') which directly contradicts the schema where 'site' is required. No explanation of 'limit' (default 100), 'cursor' pagination, or what 'site' represents.

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 verb 'List' and resource 'environment variables'. The [Enterprise] tag and license requirement help distinguish this from sibling variable tools, though it doesn't explicitly contrast with n8n_get_variable (single) vs this list operation.

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 the critical prerequisite 'Requires n8n Enterprise/Pro license', but contains a factual error claiming 'All parameters are OPTIONAL' when the schema explicitly marks 'site' as required. No guidance on when to use vs n8n_get_variable or pagination strategies.

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