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

Annotations already declare it as a read-only, non-destructive, closed-world operation. The description adds useful behavioral context: it enumerates the available topics and clarifies that an empty topic returns all of them. It does not describe the return format or content structure in detail, but given the annotations, this is sufficiently transparent.

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?

Three sentences, front-loaded with the core purpose, followed by an efficient enumeration of topics and the default behavior. No wasted words; each sentence adds necessary information.

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 knowledge-retrieval tool with one optional parameter, no output schema, and annotations covering safety, the description is complete: it explains what the tool does, what the parameter accepts, and the default return scope. Nothing essential is missing for an agent to call it correctly.

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?

With zero schema description coverage, the description fully compensates by listing all seven valid topic values (workflow_building, credentials, expressions_and_data, error_handling, webhooks, scheduling, testing) and explaining the default behavior when topic is empty. This gives an agent everything needed to supply the parameter correctly.

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 clear purpose: providing practical rules for building reliable n8n workflows. The topic list further specifies the scope, making it distinct from sibling tools that perform workflow operations. However, it does not explicitly differentiate itself from siblings like get_ai_workflow_patterns, leaving some ambiguity about when to choose this versus related knowledge tools.

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?

Implies usage for retrieving best practices and explains that an empty topic returns all topics, but gives no explicit guidance on when to use this tool versus alternatives or when to omit the topic. The calling context is inferable from the description, but proactive guidance is absent.

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