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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint:false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it returns category-bucketed examples with tool+argument shapes, it draws from the live catalog, and it can be called with no arguments or a topic. This enriches the agent's understanding without contradicting any annotation.

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 fairly long but front-loaded with common question phrasings, then moves into the output format and usage. Every sentence contributes: the synonym list helps the agent recognize user intent, the return explanation sets expectations, and the 'Use this FIRST' directive is actionable. It is slightly longer than the minimal two-sentence ideal, but appropriate for the density of information.

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 tool with one optional parameter and no output schema, the description covers purpose, return value (categories, tool+argument shape), usage variants (no-arg vs. topic), and place in the overall workflow (use first, learn meta-tools). There are no significant gaps; the agent knows exactly what to expect and when to call it.

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 coverage is 100% for the single optional parameter, so the schema already documents 'topic' with allowed values. The description adds value by showing concrete examples ('finance', 'pharma', 'betting'), explaining the default behavior when omitted ('Call with no arguments for the full spread'), and grounding the parameter in the tool's purpose. This exceeds the baseline 3.

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: 'the onboarding entry point for an agent that just connected and wants to know what is worth asking.' It specifies the exact action (returns category-bucketed example questions), the resource (Pipeworx), and the deliverable (each question paired with the exact tool + argument shape). This strongly distinguishes it from sibling tools like ask_pipeworx or discover_tools.

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 provides explicit when-to-use guidance: '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 explains the optional topic parameter and the default no-argument behavior, giving the agent a clear decision path for when to invoke this tool versus alternatives.

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