MCP Hub

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully indicates the return format (grouped by category), but fails to state whether the audit is read-only, potentially destructive, or requires specific permissions. Minimal viable disclosure for a security-related operation.

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?

Description is structurally concise with three sentences, but the '[UNIFIED]' prefix appears to be implementation metadata leaking into the description. The sentence claiming all parameters are optional wastes space on incorrect information rather than documenting the required 'site' parameter.

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 2-parameter tool with 0% schema coverage and no output schema, the description inadequately compensates. While it mentions return format (grouped by category), it fails to document parameters, misstates optionality, and omits safety characteristics essential for a security audit tool.

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, requiring the description to fully compensate. It fails to explain what 'site' represents (URL, instance ID, or name) or valid values for 'categories'. Critically, it incorrectly states 'All parameters are OPTIONAL' when the schema explicitly requires 'site', creating active confusion about the tool's interface.

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?

Clearly states the tool runs a security audit on the n8n instance and returns diagnostics grouped by category. Effectively distinguishes from sibling n8n_health_check by specifying 'security audit' versus general health checks. The '[UNIFIED]' prefix appears to be metadata noise but doesn't obscure the core 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?

Provides no guidance on when to use this tool versus alternatives like n8n_health_check, or prerequisites for running a security audit. The only usage-related statement ('All parameters are OPTIONAL') addresses parameter optionality rather than tool selection criteria.

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