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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description builds on this by detailing that the tool returns 'category-bucketed example questions' with 'exact tool + argument shape' drawn from a live catalog. 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 somewhat lengthy, but every sentence adds value: it includes example queries, explains the output format, and gives usage guidance. The list of categories is long but informative. It is well-structured with a clear flow from purpose to usage to output.

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 simplicity of the tool (one optional parameter, no output schema), the description is highly complete. It covers what the tool does, when to use it, how to use it, and what the output contains. No additional context is needed.

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%, but the description adds significant meaning beyond the schema: it explains the purpose of the optional topic parameter, lists example values (finance, pharma, etc.), and clarifies behavior when the parameter is omitted ('full spread'). The description fully compensates for the schema's minimal 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 the tool's purpose as the onboarding entry point that returns category-bucketed example questions. It distinguishes from sibling tools by explicitly noting it should be used first to learn how to call 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 explicit usage instructions: 'Use this FIRST when you do not yet know what Pipeworx can do for you' and explains the two modes (no arguments for full spread, or topic to focus). While it doesn't explicitly state when not to use, the guidance is clear and includes alternative suggestions.

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