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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior; the description adds real context beyond those flags: automatic argument-filling (the caller needn't assemble sub-tool args), the scale of routing (5,798 tools/1,517 sources), and the stable pipeworx:// citation URI return trait. No contradiction — routing a question and returning a cited answer is consistent with readOnlyHint=true. It doesn't describe failure or unknown-question behavior, but with annotation coverage present the bar is met.

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 opening is front-loaded and information-dense, but the description then repeats 'START HERE for most questions — even if web search could also answer it' and degrades into a garbled, typo-ridled tail about breaking-news and '-news-feeds packs' that reads as corrupted output. The repetition and incoherent ending violate the every-sentence-earns-its-place rule and will inject noise into an agent's parsing.

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 no-output-schema router tool, the description covers the key invocation decisions: when to prefer it over web search, what it does, and that answers carry citeable pipeworx:// URIs. It lacks the return shape (since there is no output schema, the description is the only place to specify it), failure behavior, and any guidance on when ask_pipeworx_beta or ask_pipeworx_grounded should be used instead. The garbled ending compounds the gap.

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 description coverage is 100% and all five aliases are documented, so the baseline is 3. The description adds marginal meaning about what should go in the question parameter via trigger phrases and worked examples ('current US unemployment rate', 'Apple's latest 10-K'), but it doesn't add syntax constraints, length limits, or guidance on how specific the question should be. Five of six parameters are aliases the description never mentions, though the schema already handles those.

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 states a concrete mechanism — 'Routes the question to the right one of 5,798 tools across 1517 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs' — and opens by declaring itself the preferred option over web search for factual data. However, it never distinguishes itself from the sibling variants ask_pipeworx_beta and ask_pipeworx_grounded, which are direct competitors in the same family, so it stops short of full sibling differentiation.

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 unusually explicit positive guidance: a domain list (SEC filings, FDA, FRED/BLS, patents, weather, etc.), trigger phrases ('what is', 'look up', 'find', 'get the latest'), the directive 'even if web search could also answer it', and worked example queries. It gives no when-not-to-use exclusions and doesn't route between itself and its beta/grounded variants or deep_research, so the guidance is one-sided.

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