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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context: the tool returns category-bucketed example questions with exact tool+argument shapes, drawn from the live catalog, and supports both full-spread and topic-focused calls. No contradictions 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 front-loaded with realistic user queries and packs useful detail into a single paragraph. It is somewhat long and run-on, listing many categories inline, but every part serves a purpose—clarifying scope, output content, and invocation variants. Minor structural improvements could make it scannable, but it remains efficient for the information conveyed.

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 simple tool with one optional parameter and no output schema, the description is fully complete: it states what it returns, the categories covered, how the optional parameter alters behavior, and how this tool fits into the broader tool ecosystem. The annotations and schema round out the safety and parameter details, leaving no significant gaps.

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% for the single optional 'topic' parameter, but the description enriches this by listing concrete examples ('finance', 'pharma', 'betting') and the full category list. It also explains the behavior when the parameter is omitted, which goes beyond the schema's plain description.

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 this as the onboarding entry point for an agent that just connected, listing the exact user intents it handles ('what can I ask Pipeworx?', 'getting started', 'give me ideas'). It distinguishes itself from sibling tools by explicitly stating to use it FIRST and positioning it as a gateway to meta-tools like ask_pipeworx, entity_profile, and compare_entities.

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 gives explicit when-to-use 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 optional topic filtering and no-args usage. However, it doesn't mention when not to use it or directly contrast with the sibling discover_tools, though it implies primacy.

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