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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context: the tool returns example questions drawn from a live catalog, with the exact tool and argument shape, and that calling without arguments gives a full spread while passing a topic focuses the results. This goes beyond what annotations provide.

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 concise and front-loaded with the purpose. Every sentence adds value: the first sentence states the tool's function and use cases, the second describes the output, and the third gives usage instructions. No redundant or unnecessary words.

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 complexity of the tool (returning example questions with tool shapes) and the richness of sibling tools, the description is complete. It explains the output structure, how to call it, and when to use it. The output schema is missing, but the description sufficiently describes the return value. Annotations cover behavioral aspects. Minor room for improvement: could mention that the examples are live and not static.

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% and the schema describes the 'topic' parameter. The description adds meaning by listing example values (finance, pharma, etc.) and explaining the effect of omitting it (cross-category spread), which helps an agent understand how to use the parameter correctly.

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 returns category-bucketed example questions to help users understand what Pipeworx can do. It specifies the verb 'returns' and identifies it as the onboarding entry point, distinguishing it from sibling tools like 'ask_pipeworx' or 'entity_profile'.

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 explicitly advises to use this tool first when the user does not yet know what Pipeworx can do, or to learn how to call meta-tools. It also describes how to use the optional 'topic' parameter. However, it does not explicitly state when not to use it or list alternatives, but the guidance is clear for its intended purpose.

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