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

Annotations already declare readOnly/openWorld/idempotent, and the description adds valuable context: it returns example questions with tool+argument shapes drawn from a 'live catalog', and explains behavior with or without the topic parameter. This goes beyond the annotations without contradicting 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?

The description is somewhat long (~130 words) but is front-loaded with the core purpose and packed with useful details: example queries, output structure, usage modes, and sibling tools. Every sentence contributes value, though it could be slightly tighter.

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 simple meta-tool with one optional parameter and no output schema, the description fully covers what it does, when to use it, how to invoke it, and what to expect from the output. There are no significant gaps in context.

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 fully documents the single `topic` parameter with allowed values, and the description merely repeats this with examples ('finance', 'pharma', 'betting'). Since schema coverage is 100%, the baseline of 3 is appropriate; no additional meaning is added.

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 this as 'the onboarding entry point' for agents, stating it returns 'category-bucketed example questions' with 'the exact tool + argument shape'. It distinguishes itself from siblings by prescribing 'Use this FIRST' before using meta-tools like ask_pipeworx, making the purpose unambiguous.

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 states when to use: 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools' and names specific alternatives (ask_pipeworx, entity_profile, compare_entities). This provides clear, actionable guidance.

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