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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds valuable context about the tool being an onboarding/discovery tool that returns example questions and tool call shapes, without repeating or contradicting annotations. Some behavioral details (e.g., return format) are helpful beyond annotations.

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 well-structured, front-loaded with common phrasings, and clearly explains purpose, behavior, and invocation. It is slightly verbose with repeated phrases, but every sentence adds value. Good balance of detail and brevity.

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 tool's low complexity (one optional parameter, no output schema) and rich annotations, the description thoroughly covers what the tool does, its return format, how to use it, and when to use it. No gaps are apparent.

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 description of the 'topic' parameter is identical to the schema's description. No additional meaning or clarity is added over what the schema already provides. Baseline score of 3 applies.

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: onboarding entry point that returns category-bucketed example questions with exact tool calls, drawn from the live catalog. It distinguishes from siblings by recommending use 'FIRST' and explicitly naming meta-tools like 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?

Explicitly states call with no arguments for full spread, or pass topic for focus. Provides clear when-to-use guidance: 'when you do not yet know what Pipeworx can do for you' or 'to learn how to call the meta-tools'. Effectively differentiates using context.

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