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

Annotations already mark as read-only, open-world, idempotent, non-destructive. Description adds behavioral context: it returns example questions with exact tool+argument shapes, drawn from a live catalog. No contradiction with annotations; enriches them.

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?

Description is fairly long but well-structured: starts with example queries, then explains return and usage. Every sentence adds information, but a minor reduction could improve conciseness without loss.

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 a tool with no output schema, the description fully explains the return (category-bucketed example questions with tool/argument shapes) and usage modes. Annotations cover safety, so no gaps remain.

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% for the single optional 'topic' parameter. The description adds value by listing possible values (finance, pharma, etc.) and explaining that omitting it gives a cross-category spread. Above baseline 3.

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 it's an onboarding entry point for agents new to Pipeworx, returning category-bucketed example questions. It uses specific verbs ('returns', 'draws from') and distinguishes from sibling meta-tools like ask_pipeworx by instructing 'Use this FIRST'.

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?

Explicitly says to use when 'you do not yet know what Pipeworx can do' or to learn meta-tool calling. Provides two modes: no arguments for full spread, or topic parameter for focus. No when-not needed given the clear entry-point role.

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