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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that: it discloses the specific facts surfaced (account identity, plan tier, n8n connectivity, permission flags for delete/activate), which tells the agent this doubles as a capability probe before attempting mutations. It does not mention caching, cost, or error behavior, so not a 5.

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?

Roughly two sentences, front-loaded with what the agent gets and closed with the actionable directive to call it first. The four-item enumeration is dense but each item earns its place by naming a distinct capability check. Minor redundancy in 'whether deleting/activating workflows is allowed' restating permission scope, but nothing wasteful.

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?

There is no output schema, so the description carries the burden of describing return content — and it does, enumerating the four status facts an agent would receive. Combined with zero-parameter schema and read-only annotations, an agent has enough to call this correctly and interpret the result at a high level. Exact field names and value types remain unspecified, which keeps it from a 5.

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 takes zero parameters, so per the rubric the baseline is 4. The description creates no false expectation of inputs and correctly frames this as a pure read of connection state.

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 enumerates exactly what the tool reports: the acting account, Pro plan status, whether an n8n instance is connected, and whether delete/activate operations are permitted. That is specific enough to distinguish it from every sibling (which all act on workflows, executions, nodes, or templates). It stops short of a crisp verb+resource framing ('get status of X') — 'What this connection can do right now' is an indirect lead-in — hence not a 5.

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?

Explicitly tells the agent 'Call this first in a new conversation', which is a concrete sequencing rule rather than an implied one. There is no sibling that competes for this role, so no alternatives or exclusions are needed beyond that. It does not state what to do if the call fails or what to do on a subsequent turn, keeping it at 4 rather than 5.

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