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

Annotations already provide readOnly, openWorld, and idempotent hints. The description adds meaningful behavior beyond them: it routes internally, fills arguments automatically, returns structured answers with stable citation URIs, and is described as a fast default entry point. There is no contradiction with annotations, though it does not discuss failure modes or response edge cases.

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 content is valuable but the description is overly long and contains a garbled, repetitive middle section ('default entry point, one fast call. Step up only when needed...') that duplicates routing guidance already stated earlier. It would be stronger if trimmed and cleaned up, though the key information is front-loaded.

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 has only one real parameter, rich annotations, and no output schema, the description covers most essentials: when to use it, what input looks like, what it does internally, and what kind of output to expect. The broken transition paragraph slightly undermines confidence, but overall an agent has enough guidance to invoke the 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?

The schema already documents the single required question parameter and its aliases with 100% coverage, so the baseline is 3. The description adds value by reinforcing natural-language use with concrete example queries and clarifying that aliases like q, prompt, and text are accepted. It does not deeply extend parameter semantics, but it helps an agent understand how to phrase input.

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 what the tool does: it routes a user's question to the right tool among thousands of verified sources, fills arguments, and returns a structured answer with pipeworx:// citation URIs. It also explicitly distinguishes itself from web search and sibling tools, leaving no ambiguity about 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?

The description gives unusually explicit guidance: prefer this over web search, use it for factual questions about real-world data, and START HERE for most questions. It names concrete alternatives with conditions, including ask_pipeworx_grounded for fact-checking, deep_research for multi-part queries, and web search as a last resort.

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