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

Annotations already declare safe behavior (readOnlyHint, idempotentHint, etc.). The description adds specific details about the return format: category-bucketed example questions with exact tool+argument shapes, drawn from the live catalog. It also explains the default behavior (full spread) and topic filtering. No contradiction 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 comprehensive but somewhat verbose, including many common queries in the first sentence. It is front-loaded with the purpose and usage guidance. While it could be more terse, every sentence adds value for onboarding. Minor reduction possible.

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 simplicity (one optional parameter, no output schema), the description provides complete context: what it returns, how to call it, when to use it, and a full list of categories. No gaps remain for agent decision-making.

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% with a clear parameter description listing all allowed values. The description repeats this information and adds context about usage, but adds minimal semantic value beyond the schema. Baseline 3 is appropriate.

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 that this tool returns example questions about what Pipeworx can do, organized by category, and explicitly positions it as the onboarding entry point. It distinguishes itself from siblings like ask_pipeworx and discover_tools by stating its purpose as the first tool to use.

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 says 'Use this FIRST when you do not yet know what Pipeworx can do for you', and contrasts with alternatives like ask_pipeworx, entity_profile, compare_entities. It also explains the effect of omitting vs providing the topic parameter.

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