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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the response contains category-bucketed example questions each with the exact tool + argument shape, drawn from the live catalog, which provides useful context about what to expect from the call without contradicting 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 substantive paragraph that front-loads user intent, then explains the tool's role, output contents, and calling variants. It is longer than minimal but every sentence contributes useful information, with no 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?

For a low-complexity tool with one optional parameter and no output schema, the description fully covers what the tool returns (category-bucketed examples with tool+argument shapes), how to use it (with/without topic), and when to use it (first when onboarding). No significant gaps remain.

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 single `topic` parameter is fully documented in the schema with a list of values and behavior when omitted ('Omit for a cross-category spread'). The description repeats this constraint with examples ('finance', 'pharma', 'betting') but adds little new meaning beyond the schema, so a baseline score of 3 is appropriate.

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 common user queries ('What can I ask Pipeworx? ...') and then states 'the onboarding entry point for an agent that just connected and wants to know what is worth asking.' It clearly distinguishes itself from sibling tools like discover_tools and ask_pipeworx by positioning itself as the starting point for learning about the catalog.

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 instructs '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.).' This provides explicit when-to-use guidance and names alternatives, satisfying the dimension.

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