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

The description discloses key behaviors beyond the annotations: it routes to one of 5,798 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. This adds real context about how the tool operates. The readOnlyHint, openWorldHint, and idempotentHint annotations are consistent with the described behavior, so there is no contradiction.

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 front-loaded with the most important directive: prefer this over web search for factual questions. It is lengthy because of the domain list, examples, and sibling routing, but most of that content earns its place. There is some redundancy, such as 'even if web search could also answer it' appearing twice, which keeps it from a 5.

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 a single required parameter and no output schema, the description explains the return shape well: a structured answer with stable citation URIs. It also covers the breadth of supported domains, gives concrete example queries, and routes to relevant siblings. Nothing essential 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?

Schema description coverage is 100%, and all six parameters are documented aliases for the same natural-language question field. The schema already explains that the parameter accepts query, q, prompt, text, or input as aliases. The description adds example questions but no new parameter-level semantics, so the baseline of 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 names a specific action and resource: it routes a natural-language question to the appropriate Pipeworx tool and returns a structured answer with citation URIs. It clearly distinguishes itself from siblings by naming ask_pipeworx_grounded, search_within, and deep_research, so an agent knows what this tool is and is not.

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 questions about current or historical data, and 'START HERE for most questions.' It also provides when-not-to-use routing by directing multi-step synthesis to deep_research, verbatim evidence lookup to ask_pipeworx_grounded, and pack-scoped searches to search_within.

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