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

Annotations already indicate safe, read-only, idempotent, open-world behavior. The description adds substantial context: it returns category-bucketed example questions, includes exact tool+argument shape from the live catalog, and supports full spread via no arguments or focused via topic. This reveals invocation behavior and output content 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?

Long single paragraph but densely informative; all sentences contribute value. Front-loaded with natural language query examples, though it could benefit from bullet points for readability. Not excessive given the tool's onboarding purpose.

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 one-parameter, no-output-schema tool, the description fully covers what it returns, how the parameter behaves, and when to use it. It even gives example phrasings and lists categories. No obvious gaps remain for an agent to understand invocation.

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 already documents topic with 100% coverage. Description augments by explaining that omitting topic yields a cross-category spread while passing a topic focuses results, and provides example values that align with the schema. This adds semantic understanding of how to use 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?

Description clearly states the tool's role as an onboarding entry point that returns category-bucketed example questions, each with the exact tool and argument shape. It says to use it FIRST when unfamiliar with Pipeworx, which distinguishes it from other tools, though it doesn't explicitly name sibling tools like discover_tools.

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?

Provides explicit usage guidance: '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 explains how the optional topic parameter affects breadth vs. focus. No explicit alternatives or exclusions, but the 'FIRST' placement is strong.

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