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

Annotations already cover read-only, open-world, idempotent behavior; the description adds useful non-obvious behavior: the tool is a meta-router across 5,798 tools, fills arguments on the user's behalf, emits pipeworx:// citation URIs, and can route to live news and news-feeds packs. It does not mention failure modes or latency, but the safety profile is already annotated.

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 starts with the most important directive and uses examples well, but it is one dense paragraph and contains a garbled fragment ('but schedule jest') that contributes no meaning. It could be trimmed and restructured into a clearer priority flow without losing value.

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 broad router with no output schema, it covers supported domains, example intents, return format (structured answer + stable citation URIs), and sibling handoffs, which is a complete operational picture. It does not cover empty/failed lookup behavior, but the annotations already establish the read-only, open-world nature, so the gaps are acceptable.

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%, with every parameter described as 'Alias for question', so the description does not need to restate parameter syntax. The examples show valid natural-language questions, adding marginal value, but the core semantics are fully supplied by the schema.

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 concrete action: routes a natural-language question to the right one of 5,798 tools, fills arguments, and returns a structured answer with stable pipeworx:// citation URIs. The listed domains and example questions make its scope unmistakable, and it is clearly positioned against web search and sibling research tools.

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?

It explicitly says to prefer this over web search for factual queries, gives trigger phrases ('what is', 'look up', 'find', 'get the latest', 'current'), and points to alternatives with conditions: ask_pipeworx_grounded for a grounded single answer, deep_research for broad/multi-part questions. The 'START HERE' directive tells the agent this is the default entry point.

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