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

Annotations already declare this a read-only, open-world, idempotent operation. The description adds that it draws from the live catalog of thousands of tools and returns exact tool+argument shapes, which is valuable behavioral context beyond 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 long but information-dense, front-loaded with example user queries, and each clause adds specific detail about categories, return format, and usage. Slight redundancy with the schema but overall efficient for a tool of this complexity.

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 tool with one optional parameter and no output schema, the description fully covers what it returns, how to invoke it, and when to use it. It also names the meta-tools it can teach, making the context complete.

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 describes the topic parameter with enum-like values and instructions to omit for a cross-category spread. The description reinforces with concrete examples ('finance', 'pharma', 'betting') and the same omission guidance, adding modest value beyond the schema.

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 defines the tool as the onboarding entry point that returns category-bucketed example questions with the exact tool and argument shape. It distinguishes from siblings by explicitly mentioning meta-tools and focusing on 'what can I ask.'

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 provides explicit usage guidance: 'Use this FIRST when you do not yet know what Pipeworx can do for you.' It also explains the optional topic parameter for focusing, giving clear context for when to use it versus when to call with no arguments.

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