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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds behavioral context: it returns category-bucketed example questions with exact tool+argument shapes drawn from a live catalog, and that calling with no argument gives a full spread. No contradictions with 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 dense but every sentence contributes unique value: aliases, use case, output format, parameter guidance, and placement in the agent's workflow. It is well-structured with no filler or redundancy.

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 simplicity (1 optional param, no output schema), the description is fully self-contained. It explains what the tool returns, how to invoke it, and the variety of categories, compensating for the lack of output schema. It provides complete information for an agent to select and use this tool 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 coverage is 100% (topic described). The description enhances parameter meaning: explicitly states 'omit for full spread', provides concrete examples of topics ('finance, pharma, betting'), and explains the effect of the parameter on the output, going beyond the schema's brief description.

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 uses a specific verb-resource pair ('suggest questions' about 'what Pipeworx can do') and lists multiple aliases. It clearly distinguishes from sibling tools by positioning itself as the onboarding entry point, contrasting with tools like discover_tools or ask_pipeworx.

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 when to use ('FIRST when you do not yet know what Pipeworx can do') and when not (implies after you know, use other tools). Name-drops specific sibling meta-tools (ask_pipeworx, entity_profile, etc.) and explains how the results help learn tool calls.

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