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

Annotations already cover read-only, open-world, idempotent, and non-destructive. The description adds significant behavioral context: it pulls from the 'live catalog of thousands of tools', returns category-bucketed examples with exact tool/argument shapes, and explains behavior with or without the `topic` parameter. This goes well beyond the 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 a single dense paragraph that front-loads the key question it answers, then details return format and optional input. It is longer than minimal but every sentence adds value for a discovery tool, so it earns a 4 rather than a 5.

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?

With no output schema and low complexity, the description gives complete context: what it returns (category-bucketed examples), how it behaves (live catalog, exact tool+arg shape), and when to use it (first/onboarding). This fully covers the tool's usage context.

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 description already documents the single optional `topic` parameter with its categories and the omit-for-full-spread behavior. The description rephrases these examples ('finance', 'pharma', 'betting') without adding new syntax or semantics, so the baseline of 3 applies given high schema coverage.

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 states the tool is 'the onboarding entry point' that returns 'category-bucketed example questions' with 'the exact tool + argument shape' for each. This specific verb+resource framing clearly differentiates it from siblings by positioning it as the first tool to use when unfamiliar with Pipeworx.

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 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools'. This provides strong when-to-use guidance, but it lacks explicit when-not-to-use or alternative tool recommendations beyond learning, so it's not a full 5.

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