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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds valuable behavioral context: it is the onboarding entry point, returns categorized example questions with tool/argument shapes, and can be called with no arguments for full spread or with a topic to focus. 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 a single paragraph starting with a list of example user intents, which is slightly redundant but still adds context. It efficiently conveys purpose, usage, and output structure in about 100 words. Could be more structured (e.g., bullet points for topic options), but overall concise and clear.

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 lack of an output schema, the description adequately explains that the return is category-bucketed example questions with tool and argument shapes. It covers parameter behavior and states the tool's role as an onboarding entry point. No critical missing information for an agent to use it effectively.

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% and the schema already describes the optional topic parameter. The description enhances this by providing concrete examples ('e.g. 'finance', 'pharma', 'betting') and explaining the behavior difference between omitting (full spread) and passing a topic (focus). This adds meaning beyond the schema alone.

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 as the onboarding entry point that returns category-bucketed example questions with exact tool + argument shape, explicitly distinguishing it from siblings by advising 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools.' The verb and resource are specific and distinct from siblings like ask_pipeworx or discover_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?

The description gives clear context for when to use: 'when you do not yet know what Pipeworx can do' and 'to learn how to call the meta-tools.' It also explains how to pass an optional topic to focus. However, it does not explicitly state when not to use it or list alternative tools for specific scenarios, though the context implies usage for initial exploration.

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