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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, providing a safety profile. The description adds valuable behavioral context: it returns live catalog data, organizes results by category, and supports optional topic filtering. It also clarifies the output shape (example questions with tool+argument pairs), going beyond what annotations alone convey.

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?

Though long, every sentence in the description earns its place. It front-loads the example queries, then concisely explains the output, the catalog source, the optional parameter, and the recommended usage. The structure is logical and free of fluff.

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 an onboarding tool with no output schema, the description is remarkably complete. It explains what the tool returns, how to invoke it (with or without a topic), when to prioritize it, and what meta-tools it teaches. The rich annotations further reduce the need for extra safety disclaimers.

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 already describes the optional 'topic' parameter with allowed values, so baseline is 3. The description adds extra semantics by giving concrete examples (finance, pharma, betting) and explaining the default behavior when the parameter is omitted ('full spread'). This enriches the meaning beyond the schema.

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 states the tool's purpose: it is the onboarding entry point that returns category-bucketed example questions, each with the exact tool and argument shape. It distinguishes itself from siblings by positioning as a first-stop discovery tool and explicitly names meta-tools like ask_pipeworx, entity_profile, and compare_entities.

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 usage 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 clearly indicates when to use it, though it does not explicitly state when not to use it. The context is sufficient for an onboarding tool.

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