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

Beyond the readOnly/idempotent annotations, the description explains it draws from a live catalog of thousands of tools, returns category-bucketed example questions with the exact tool and argument shape, and supports a topic focus. This gives substantial context about the tool's behavior and output beyond what annotations provide.

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 longer than average but every sentence adds value: it lists example prompts, states the purpose, describes the output, and gives usage guidance. It front-loads the user intent and is well-structured, though slightly verbose due to the introductory prompt examples.

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?

With no output schema, the description fully explains return values: category-bucketed example questions across listed domains, each with the tool and argument shape. It also covers parameter behavior and the onboarding use case, making it complete for a simple read-only 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 coverage is 100%, so the parameter is fully documented. The description adds meaningful use context by explaining 'Call with no arguments for the full spread, or pass topic to focus' and provides examples ('finance', 'pharma', 'betting'), clarifying the default and filtering behavior.

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 clearly states it is the onboarding entry point that returns category-bucketed example questions, and distinguishes itself from meta-tools like ask_pipeworx, entity_profile, and compare_entities. It uses a specific verb ('suggest questions') and identifies the resource (Pipeworx capabilities).

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 instructs 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools...' It also shows example prompts that trigger the tool and notes the optional topic parameter, giving clear when-to-use guidance and naming alternatives.

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