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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds valuable behavioral context beyond that: it returns category-bucketed example questions, includes the exact tool and argument shape for each, and is drawn from a live catalog. It also clarifies that calling with no arguments returns the full spread, which is a behavior not evident from annotations alone.

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 long but rich with examples and usage guidance. It front-loads the most important query phrases, then explains the return format and call variations. Every sentence contributes to understanding the tool's value and use, though it could be tightened slightly without losing substance.

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?

Despite having no output schema, the description thoroughly explains what the tool returns (category-bucketed example questions with tool+argument mappings), how it behaves with and without the optional topic parameter, and when to use it. This is highly complete for an onboarding/discovery tool, covering purpose, usage, and behavior comprehensively.

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 already provides 100% coverage for the single `topic` parameter with a description and explicit enumeration of valid values. The description only restates the optional nature and gives a few examples, adding minimal semantic value beyond the schema. Baseline 3 applies because schema coverage is complete.

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: it's the onboarding entry point for agents wanting to know what questions to ask Pipeworx. It enumerates example query types and explicitly distinguishes itself from related tools by noting it provides exact tool + argument shapes, making it 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 explicit use cases: 'Use this FIRST when you do not yet know what Pipeworx can do for you' and 'to learn how to call the meta-tools'. It also explains the optional `topic` argument for focused queries. However, it doesn't explicitly state when NOT to use this tool (e.g., when you already know the exact tool to call), so it misses a clear exclusionary statement.

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