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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, so the description need not repeat safety. It adds behavioral context beyond the annotations: the tool acts as an orchestrator that routes to sub-tools, fills arguments, and returns stable pipeworx:// citation URIs, which is exactly the kind of extra behavior an agent should know. 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 longer than average but front-loads the key directive ('PREFER OVER WEB SEARCH'), then moves through supported domains, mechanism, trigger phrases, examples, and alternatives in a logical order. It is dense with useful information; a small trimming of domain lists would improve conciseness, but every sentence contributes to selection/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?

For a meta-tool with no output schema, the description covers what to pass (question), what to expect (structured answer with citation URIs), when to use it (most factual queries, even over web search), and when to divert to siblings (grounded/deep_research). No output schema means return-value expectations are still adequately set by 'structured answer with stable citation URIs'. The tool's complexity is high, yet nothing critical is missing for an agent to invoke it 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?

The input schema already documents the sole required 'question' parameter and five aliases with 100% coverage, which sets a baseline of 3. The description adds practical parameter meaning via concrete query examples and trigger phrases ('what is', 'look up', 'find') that clarify what kind of natural-language input to pass, helping the agent construct valid calls. It does not detail length/format limits, but those are not essential for a free-text query tool.

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?

States precisely that ask_pipeworx is a routing tool: it takes a natural-language question, selects one of 5,743 tools across 1,500 verified sources, fills arguments, and returns a structured answer with stable pipeworx:// citation URIs. It also distinguishes itself from siblings (ask_pipeworx_grounded, deep_research) and frames itself as 'START HERE', so an agent can identify its role.

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 tells the agent to prefer this over web search for a long list of factual data categories, and gives 'Use whenever' trigger phrases. It also states exclusions/alternatives: use ask_pipeworx_grounded for hallucination-resistant single answers with evidence, and deep_research for broad multi-part questions requiring fan-out, plus notes it already covers live-news queries.

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