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

Annotations already provide readOnly, openWorld, and idempotent hints. The description adds meaningful context: it returns category-bucketed example questions, draws from the live catalog of thousands of tools, and lists the exact output content. No contradiction with 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 dense and front-loaded with example phrasings, but remains well-organized with em-dashes and a clear flow. Every sentence contributes, though the length is on the higher side for a tool with one optional 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?

Covers purpose, invocation modes, output contents (bucketed questions with tool shapes), and relationship to sibling tools. Even without an output schema, the description fully explains what to expect and when to call 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 single optional parameter `topic` is fully documented in the schema, including the enum-like list and the omit behavior. The description adds only minor examples ('finance', 'pharma', 'betting') without introducing new syntax or semantics, so the baseline of 3 is appropriate.

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 that returns category-bucketed example questions with exact tool and argument shapes. It distinguishes itself from sibling meta-tools like ask_pipeworx and discover_tools by emphasizing 'Use this FIRST'.

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 states when to use: 'Use this FIRST when you do not yet know what Pipeworx can do for you,' and names alternatives like ask_pipeworx, entity_profile, and compare_entities. Also explains invocation modes: no args for full spread or pass a topic to focus.

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