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

Annotations already declare read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: it explains the tool returns category-bucketed example questions with exact tool+argument shapes from a live catalog, and that it can be focused by topic. This goes beyond the annotation baseline.

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 somewhat long but well-structured: it opens with user-intent phrases, explains the return format, then covers usage and parameter behavior. Every sentence contributes necessary onboarding information, though a few category examples could be trimmed.

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 fully communicates what the tool returns: category-bucketed example questions with the exact tool and argument shape. It covers invocation modes (no args vs topic) and the broader use case of learning meta-tools, making it self-sufficient for an agent.

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 coverage is 100% with a good description for the topic parameter, but the tool description enriches semantics by explaining that omitting the parameter yields a full spread while providing it focuses the results. This adds value beyond the schema's 'Optional focus area' phrasing.

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 states it is an onboarding entry point that returns example questions and maps them to tools, with a specific verb and resource. It distinguishes itself from sibling tools like discover_tools by positioning as 'Use this FIRST' and mentioning meta-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?

Explicitly says '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 the tradeoff between calling with no arguments versus passing a topic, providing clear context for when to use each mode.

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