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

Annotations already cover readonly, open-world, idempotency, and non-destructiveness. The description adds context about the output structure (category-bucketed examples, exact tool + argument shape) and the effect of the topic parameter. It doesn't contradict annotations and provides useful non-obvious details about the returned data.

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 long sentence but well-structured with dashes and examples. It front-loads the key phrases and packs useful details without repetition. While it could be split into shorter sentences, every clause contributes meaning, keeping it reasonably concise given the tool's coverage.

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?

Despite lacking an output schema, the description thoroughly covers the return type (category-bucketed example questions, exact tool + argument shape), the data source (live catalog of thousands of tools), and invocation modes (no args vs topic). It also ties into meta-tool discovery, making it fully self-contained for a new user.

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's topic description is simple and covered 100%, so baseline is 3. The description adds value by listing concrete topic examples ('finance', 'pharma', 'betting') and explaining that omitting the parameter yields a cross-category spread, giving practical guidance not in 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: the onboarding entry point for Pipeworx, returning category-bucketed example questions with exact tool-argument shapes. It uses specific verbs ('returns', 'focus') and draws on a live catalog, and it distinguishes itself from siblings by explicitly marking its first-use role and by mentioning meta-tools (ask_pipeworx, entity_profile, 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 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 usage modes (no arguments for full spread, pass topic to focus). It does not explicitly discuss when-not-to-use or name comparing alternatives, but the guidance is clear enough.

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