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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, and the description adds behavioral context about return structure (category-bucketed example questions with tool + argument shape drawn from the live catalog) and argument variability (no args vs topic). This exceeds the safety-only info from annotations, but doesn't describe output schema details or edge cases.

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 but well-structured, front-loading with user utterances that signal purpose, then explaining behavior, usage, and positioning. Every sentence contributes; no filler. It could be tightened but is appropriately detailed for a complex tool with an optional filter.

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 read-only tool with one optional parameter and no output schema, the description fully covers the return value (category-bucketed examples), the parameter semantics, and the intended usage context (first stop after connecting). It also addresses the common 'what data do you have?' question. Complete enough to invoke correctly.

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 covers the single optional `topic` parameter with full enum description, so baseline is 3. The description adds examples ('finance', 'pharma', 'betting') and clarifies that omitting returns a cross-category spread, but this largely restates schema info. Little additional semantic value beyond schema.

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 this is the 'onboarding entry point' for suggesting what questions to ask Pipeworx, with a verb-object-resource structure. It distinguishes itself from sibling tools by positioning as 'Use this FIRST' and explicitly references meta-tools it teaches (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?

Provides explicit usage guidance: 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools'. It also explains the optional topic parameter behavior ('Call with no arguments for the full spread, or pass topic to focus'). While it doesn't state explicit 'when not', the 'FIRST' instruction and alternative meta-tool names give clear context.

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