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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds behavior beyond that: outputs are drawn from the live catalog, results are organized by category, each example carries the tool+argument shape, and calling with no arguments returns the full spread while passing topic focuses. This meaningfully supplements the annotations without contradiction.

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?

Although longer than minimal, the description is front-loaded with purpose and every section earns its place: trigger phrases for what users might ask, the return value summary, the optional parameter behavior, and explicit first-use guidance. It is dense but not bloated.

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 explaining return values. It clearly states that results are category-bucketed example questions with exact tool and argument shape. It also covers the optional topic behavior, the categories available, and usage context, making the tool fully usable from the description alone.

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 schema already covers the single optional `topic` parameter at 100%, so the baseline is 3. The description adds extra meaning by giving concrete examples ('finance', 'pharma', 'betting') and explaining the no-argument vs. topic-focused call pattern, which helps the agent decide how to populate the parameter.

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 identifies the tool as the onboarding entry point for a newly connected agent and says it returns category-bucketed example questions with the exact tool and argument shape needed to answer them. This distinguishes it from siblings like discover_tools or ask_pipeworx by focusing on 'what to ask' rather than just listing tools or answering a specific query.

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?

It explicitly says 'Use this FIRST when you do not yet know what Pipeworx can do for you' and explains that it can also teach how to call meta-tools like ask_pipeworx, entity_profile, and compare_entities. It doesn't explicitly state when NOT to use it, but the wording implies this is the starting point before using those more targeted tools, which counts as clear context.

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