n8n_get_instance_version

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

With no annotations available, the description carries the full burden. The word 'obtener' (get) implies a safe read operation, but no additional behavioral context is provided, such as response structure, authentication requirements, or potential side effects. This is minimally adequate for a simple getter.

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 a single concise sentence with no redundant words. It effectively communicates the tool's purpose in minimal space.

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 zero-parameter tool, the description is largely complete. It covers what the tool retrieves, though it does not differentiate from n8n_get_instance_info, leaving some ambiguity in selection. The absence of an output schema means the description should mention return values, which it partially does by naming 'version and settings.'

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 tool has zero parameters, so the baseline score is 4. The description adds clarity about the output (version and settings), but there are no parameter semantics to explain.

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 'Obtener versión y ajustes de la instancia n8n' clearly indicates the tool retrieves version and settings, with a specific verb and resource. However, it does not distinguish itself from the sibling tool n8n_get_instance_info, which likely overlaps in purpose.

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 is provided on when to use this tool versus alternatives like n8n_get_instance_info. The description is purely declarative and lacks any contextual cues about appropriate use cases or prerequisites.

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