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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the description does not need to restate safety. It adds useful behavioral context: returns live-catalog-derived example questions with exact tool and argument shapes, and describes the parameter behavior (omit for full spread, pass topic to focus). No contradiction.

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 longer than the average but every sentence adds value. It front-loads common queries, states purpose, then gives return details and usage guidance. 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?

For a zero-required-param tool with no output schema, the description fully covers what to expect: the returned structure (category buckets), content (example questions with tool+argument shape), and the optional topic parameter's effect. It also provides usage context relative to other tools.

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?

Input schema fully covers the `topic` parameter with a description. The tool description adds concrete examples ('finance', 'pharma', 'betting') and clarifies the output scope for omitted vs. provided topic, going beyond the schema's enum-like list.

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 identifies the tool as an onboarding entry point that returns category-bucketed example questions, with a specific verb ('suggest') and resource (what to ask Pipeworx). It differentiates from sibling meta-tools by positioning itself as the first step, which also distinguishes it from other query tools.

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?

Provides explicit guidance: 'Use this FIRST when you do not yet know what Pipeworx can do for you' and explains the alternative of passing a topic to focus. It implies when to use vs. meta-tools by naming them (ask_pipeworx, entity_profile) as things you learn about here.

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