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

Annotations already provide safety traits (readOnly, non-destructive, idempotent). The description adds valuable behavioral context: it returns category-bucketed example questions, each with the exact tool and argument shape, drawn from the live catalog of thousands of tools. This goes beyond annotations by describing the output structure and dynamic nature, without contradicting the annotations.

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 appropriately detailed and front-loaded, starting with example queries and then the core purpose. It's a bit long but every sentence adds value, including the return format and customization options. The list of categories mirrors the schema but is still useful for quick scanning.

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 must explain return values, and it does: category-bucketed example questions with tool and argument shapes. It also covers use cases, the topic parameter, and the dynamic nature of the catalog. It is complete enough for an agent to understand when and how to invoke this 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?

The schema already provides 100% coverage for the single 'topic' parameter, listing all valid values. The description merely repeats examples ('finance', 'pharma', 'betting') without adding new information. The baseline is 3 for high schema coverage, and the description does not enhance parameter understanding.

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 an onboarding entry point that returns category-bucketed example questions with the exact tool and argument shape to answer them. This specific verb+resource structure distinguishes it from sibling tools like ask_pipeworx or discover_tools, and it explicitly states what it does and how it's different.

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?

The description explicitly tells the agent to use this tool FIRST when it doesn't know what Pipeworx can do, and it names meta-tools to learn about. It also explains how to customize with the topic parameter. However, it doesn't explicitly state when NOT to use it or directly contrast it with alternatives, so it falls short of a 5.

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