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 value by explaining the output content (category-bucketed example questions with tool+argument shapes) and that it is drawn from the live catalog, which goes beyond annotation-only context.

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, long sentence with examples and usage, but every clause adds essential information. It is front-loaded with example queries and the core purpose, and while somewhat dense, it avoids redundancy or filler.

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 tool has no output schema, the description adequately explains the return type (category-bucketed example questions) and the parameter behavior. It also provides enough onboarding context for an agent. A perfect score would require additional detail on response structure or pagination, but overall it is complete for its purpose.

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 covers 100% of the parameter, listing the allowed values. The description supplements this with concrete examples ('finance', 'pharma', 'betting') and explicitly states that omitting `topic` gives a cross-category spread, adding meaning 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 the tool's purpose as 'the onboarding entry point' that returns category-bucketed example questions with exact tool and argument shapes. It uses specific verbs ('returns', 'call') and distinguishes itself from siblings by instructing to 'Use this FIRST' when unsure of Pipeworx capabilities.

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?

Explicitly says when to use: '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 clarifies the optional `topic` parameter usage. However, it does not explicitly name alternative tools like discover_tools, so it lacks an explicit exclusionary comparison, earning a 4 rather than a 5.

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