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

Annotations already declare readOnlyHint and idempotentHint. The description adds meaningful behavioral context: results are drawn from the live catalog of thousands of tools, output is category-bucketed with tool mappings, and calling with or without topic changes scope. These details go beyond what annotations alone provide.

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 longer than necessary, with a six-item list of example questions and a full category enumeration, but each section serves a purpose: examples aid pattern-matching, categories set expectations, and usage instructions are clear. It could be trimmed slightly without losing impact.

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 compensates by explaining what is returned (category-bucketed example questions with tool and argument shape), how to call it (no args vs topic), and when to use it. It also covers the meta-tool learning angle, making it complete for an onboarding tool.

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 input schema already provides 100% coverage for `topic` with full enum list and omission guidance. The description's mention of examples ('finance', 'pharma', 'betting') and 'no arguments for the full spread' adds no new semantic info 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 states the tool returns category-bucketed example questions with exact tool and argument shape, and identifies itself as the onboarding entry point. It distinguishes from sibling tools like ask_pipeworx and entity_profile by focusing on 'what is worth asking' and teaching how to call 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?

It 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,' and names alternatives (ask_pipeworx, entity_profile, compare_entities). This provides clear when-to-use and alternative guidance.

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