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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior, so the bar is lower. The description adds meaningful behavioral context: it routes to 5,936 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. It does not mention failure modes or rate limits, but the safety profile is already handled by 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 long but front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and organized with a clear hierarchy: what it does, when to use, examples, when to step up. A small amount of redundancy exists around 'prefer over web search' / 'even if web search could also answer' / 'START HERE', but the repetition reinforces the core routing guidance.

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?

There is no output schema, so the description appropriately explains the return shape: a structured answer with stable pipeworx:// citation URIs. It covers supported domains, example queries, alternative tools, tier availability, and even handles breaking-news use cases. Nothing critical is missing for an agent to decide whether and how to invoke it.

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 question parameter is well documented with aliases. The description goes beyond the schema by clarifying that the agent only needs to supply the question and that PipeWorx will fill the remaining arguments itself, plus giving example natural-language queries that demonstrate expected input style.

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 defines a specific action: routing a natural-language question to the right PipeWorx tool among thousands and returning a structured, cited answer. It distinguishes itself from siblings by positioning itself as the default entry point and explicitly naming ask_pipeworx_grounded and deep_research as the step-up alternatives.

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 gives explicit when-to-use guidance: prefer over web search for factual/structured data, use for common question phrasings like 'what is', 'look up', 'get the latest', and provides concrete examples. It also states when NOT to use it and which sibling to step up to for grounded single answers or broad multi-part research.

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