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

The description adds meaningful behavioral context beyond the annotations. It discloses that the tool returns category-bucketed examples, drawn from a live catalog of thousands of tools, and explains the parameter behavior (no args for full spread, topic for focus). It does not contradict the readOnly, openWorld, or idempotent hints. Slightly less transparency around edge cases, but the provided context is sufficient.

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 efficient and information-dense, covering purpose, output, usage, and context in about 100 words. It front-loads with example user queries to quickly orient the reader. While slightly dense, every sentence earns its place, and there is 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?

Given the lack of an output schema, the description fully explains what the tool returns (category-bucketed example questions with tool+argument shapes) and how to call it. It also covers when to use it and what to expect from the live catalog. For a tool with one optional parameter, this is complete and leaves no significant gaps.

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 fully documents the 'topic' parameter with a list of valid values and the behavior of omitting it for a cross-category spread. The description repeats this with examples (e.g., 'finance', 'pharma', 'betting') but adds no new semantic information. With 100% schema coverage, the description does not need to compensate, so a baseline 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 clearly states that this tool is the onboarding entry point for an agent to learn what to ask Pipeworx, returning category-bucketed example questions with exact tool and argument shapes. It distinguishes itself from siblings by explicitly saying 'Use this FIRST' and referencing meta-tools like ask_pipeworx, making its unique role clear.

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 mentions specific alternative tools (ask_pipeworx, entity_profile, compare_entities) and how to invoke the tool with or without the topic parameter, covering both context and variations.

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