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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description doesn't need to restate safety. It adds valuable behavioral context: the tool draws from a 'live catalog of thousands of tools,' returns category-bucketed examples, and that each example includes the exact tool+argument shape. This explains what the agent will receive and why it is a useful onboarding tool beyond what annotations convey.

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 but every sentence contributes useful information: user-intent phrasings, purpose, return contents, category list, parameter behavior, and a clear usage directive. It's somewhat long and starts with a run-on list of user queries, but it front-loads recognizability and remains information-dense without significant redundancy.

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?

Given the tool's low complexity (one optional parameter, no output schema), the description is remarkably complete. It explains the purpose, what the agent will receive (category-bucketed examples with tool+argument shapes), how to invoke it (with or without topic), and when to use it (first, when onboarding). It even positions it relative to sibling meta-tools, making selection unambiguous.

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 description coverage is 100%: the schema already documents the optional `topic` parameter with its allowed values and the behavior when omitted. The description adds example values ('finance', 'pharma', 'betting') and reinforces the call-with-no-arguments behavior, but this is marginal value beyond the schema. Baseline 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 this as the onboarding entry point for the Pipeworx agent, explicitly stating it returns category-bucketed example questions with the exact tool and argument shape to answer them. It distinguishes itself from siblings by positioning itself as the 'first' tool to use when the agent doesn't know what Pipeworx can do, and it even names the more specific meta-tools like ask_pipeworx and entity_profile.

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 an explicit usage directive: '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 provides invocation guidance for the optional topic parameter and describes the no-argument behavior. While it doesn't list every 'when-not' scenario, the 'first' framing implicitly tells the agent to move on to more specific tools once it has learned what's available.

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