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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral detail: it returns category-bucketed questions with exact tool+argument shapes drawn from the live catalog. This complements annotations without contradiction.

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 a single paragraph that packs essential information: alternative query phrasings, purpose, output content, and usage guidance. It is front-loaded with common questions. While dense, it is clear and not overly verbose for the complexity of an onboarding tool.

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 role as an onboarding entry point, the description covers all key aspects: when to use, optional parameter, output description (categorized questions with tool+argument shapes), and relation to sibling tools. No output schema exists, but the description sufficiently explains the return type.

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 describes the 'topic' parameter. The description adds value by listing example topics (e.g., 'finance', 'pharma', 'betting') and explaining that omitting the parameter gives a cross-category spread. This enriches the schema's basic 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 states that the tool is an onboarding entry point that returns category-bucketed example questions with exact tool call shapes. It distinguishes from sibling tools by being the first tool to use when unfamiliar with Pipeworx, and explicitly contrasts with 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 explicitly says 'Use this FIRST when you do not yet know what Pipeworx can do for you' and explains when to pass the optional topic parameter (to focus) or omit for full spread. It also mentions learning to call meta-tools, providing clear guidance on when and how to use this tool versus alternatives.

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