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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's disclosure of returns (live tool shapes, category buckets) adds useful context without redundancy. The description also notes that the output is drawn from a live catalog, implying up-to-date results.

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 well-structured, front-loading alternative phrasings and the tool's role. It lists categories in both description and schema, which is slightly redundant but not overly verbose. Each sentence serves a purpose: introduction, output description, usage instructions, and when-to-use guidance.

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 an onboarding tool with rich annotations and a fully described schema, the description is complete. It explains the output format, the effect of the optional parameter, and the tool's place in the workflow (first step). No output schema is needed given the straightforward return pattern.

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 schema fully covers the parameter with 100% description coverage, listing enum values. The description adds value by showing usage patterns (omit for full spread, pass a topic to focus) and providing illustrative examples like 'finance', 'pharma', which reinforce the schema's enum list.

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 explicitly states the tool's purpose: returning category-bucketed example questions with exact tool call shapes. It differentiates from sibling tools like ask_pipeworx by positioning itself as the onboarding entry point to discover what to ask. The alternative phrasings ('what can I ask Pipeworx?', 'give me ideas') further clarify intent.

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?

Clear guidance is provided: 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools.' This sets expectations for when to invoke the tool versus query tools. It also explains how to use the topic parameter to narrow focus.

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