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

Annotations already cover safety (readOnly, openWorld, idempotent, non-destructive). The description adds valuable behavioral context: it draws from the live catalog, returns exact tool and argument shapes, and supports topic-based focusing. No contradictions with 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 long but well-structured, front-loaded with sample user phrases and organized with a clear flow: intent → return value → invocation options → when to use. No wasted filler, though it could be tightened slightly without losing value.

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, the description fully covers the return format (category-bucketed examples with tool+argument shapes), invocation variants (no args vs topic), and usage context. It also mentions how to learn meta-tool usage, making it self-sufficient for onboarding.

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% with a detailed description of the optional topic parameter, including enum-like values and omit-for-spread behavior. The description adds examples ('finance', 'pharma', 'betting') and the word 'focus', but these are essentially redundant with the schema, so baseline 3 applies.

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 explicitly identifies this as the onboarding entry point for a newly connected agent, listing the exact user intents it serves (e.g., 'what can I ask Pipeworx?'). It clearly differentiates from siblings like discover_tools or ask_pipeworx by stating it returns category-bucketed example questions with exact tool+argument shapes.

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?

Provides explicit guidance: 'Use this FIRST when you do not yet know what Pipeworx can do for you' and explains how to call with no arguments vs. a topic. However, it does not explicitly mention when not to use it or name alternatives for exclusion, though referencing meta-tools implies their use for other purposes.

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