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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: that the tool returns example questions drawn from a live catalog of thousands of tools, and that it can be called with or without a topic parameter. This goes beyond the annotations without contradicting them.

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 with a list of acceptable variations at the start, followed by a clear explanation of output and usage. It is somewhat long but every sentence adds value; could be slightly more condensed by removing the full category list, but the list is informative.

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 provides complete context: what the tool does, when to use it, what input to provide, and what output to expect. It also mentions meta-tools, fully covering the onboarding use case.

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% for the single 'topic' parameter. The description adds meaning by listing example values (finance, pharma, etc.) and clarifying that omitting the topic returns a cross-category spread, while providing one focuses on a specific area. This adds functional understanding 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 that this tool is the onboarding entry point for an agent to learn what questions to ask Pipeworx. It specifies the output (category-bucketed example questions with exact tool+argument shape) and distinguishes itself from sibling tools like ask_pipeworx and entity_profile by its role as a discoverability aid.

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, or to learn how to call the meta-tools'. It also explains when to call with no arguments vs. with a specific topic, providing clear context for when to use this tool over alternatives.

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