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

Annotations already declare readOnlyHint/idempotentHint, and the description adds useful behavior: results are drawn from the live catalog, are category-bucketed, and include the exact tool + argument shape for each example. It doesn't mention output limits or pagination, but it goes beyond the structured hints enough to warrant a 4.

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 longer than average, but every sentence carries operational value: example phrasings, return contents, call modes, and when to use first. It is front-loaded with the user's likely questions and remains free of filler, though it could be tightened slightly.

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 only one optional parameter, no output schema, and complete annotations, the description fully covers what an agent needs: what will be returned, how to request the full spread vs. focused output, and when to invoke the tool. It is complete for this low-complexity onboarding tool.

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?

Although the schema already names the optional 'topic' parameter, the description adds practical semantics: examples ('finance', 'pharma', 'betting'), the effect of passing a topic ('focus'), and the crucial behavior of omitting it ('full spread'). This meaningfully exceeds the schema description.

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 opens with concrete example queries and clearly identifies this as 'the onboarding entry point' that 'Returns category-bucketed example questions'. The verb 'Returns' plus the scope (what can I ask Pipeworx) distinguishes it from siblings like discover_tools and makes the intended purpose unmistakable.

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?

It explicitly states 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 (ask_pipeworx, entity_profile, compare_entities, etc.)'. It also gives clear call-mode guidance: no args for the full spread versus passing topic to focus.

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