n8n: Get project

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

Annotations already declare readOnlyHint=true, so safety is covered and the bar is lower. The description adds the licensing/auth precondition, which is real value beyond the annotations, but says nothing about failure behavior (missing project, permission denied) or whether the lookup is scoped to a single instance.

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 segments with the action front-loaded and the prerequisite trailing; nothing is wasted. The bracketed tags are noisy but scannable and take little 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 two-parameter read with no output schema, the description covers purpose and licensing but leaves two meaningful gaps: what 'site' refers to (which n8n instance) and what a successful response contains. Adequate but not fully self-sufficient.

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 the description must carry parameter meaning. 'By ID' does clarify that project_id is a raw identifier rather than a name, and the Enterprise note explains the licensing context for the whole call. The second parameter, 'site', remains entirely unexplained.

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 a specific verb and resource ('Get project details by ID'), which cleanly separates it from sibling mutations like n8n_create_project, n8n_update_project and n8n_delete_project. The '[UNIFIED] [Enterprise]' prefixes are opaque tags rather than purpose information, but the core sentence is unambiguous.

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?

The license prerequisite ('Requires n8n Enterprise/Pro license') is a genuinely useful precondition that tells the agent when the call can succeed. However, there is no explicit guidance on when to fetch a project vs. using a list/search alternative, and no statement of what happens with an unknown ID.

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