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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds meaningful behavioral context about the output: it returns category-bucketed example questions with 'the exact tool + argument shape' drawn from the live catalog, and explains the no-argument vs. topic-focused behavior. This goes beyond the structured 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 longer than strictly necessary, but it is front-loaded with example queries and then structured into purpose, output, parameter behavior, and usage guidance. Every section earns its place, though the sentence containing the full category list is somewhat dense; still, it remains efficiently organized.

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's simplicity (one optional parameter, no output schema), the description is complete: it explains what the tool returns, the categories covered, how the parameter modifies behavior, and when to use it. The absence of an output schema is compensated by the description clearly stating the output structure (category-bucketed example questions with tool+argument shapes).

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 covers 100% of the single `topic` parameter, listing all valid values and the omit behavior. The tool description adds only marginal redundancy by naming a few example topics ('finance', 'pharma', 'betting'), so it does not significantly enhance parameter understanding beyond what the schema provides.

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 identifies this as the onboarding entry point for an agent that just connected, with a specific verb ('Returns category-bucketed example questions') and resource (Pipeworx's tool catalog). It distinguishes itself from siblings by explaining it teaches how to call meta-tools like ask_pipeworx, entity_profile, and compare_entities, which no other sibling does.

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 explicitly states when to use it: '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 provides clear context and direction, though it does not explicitly name alternative tools or when not to use it, which would raise it to a 5.

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