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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so no contradiction exists. The description adds useful behavioral context beyond annotations by explaining that the tool routes questions, fills arguments, and returns stable pipeworx:// citation URIs. It could add more about output limits or error behavior, but the safety profile is already covered.

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 long but front-loaded with the most important instruction ('PREFER OVER WEB SEARCH'), followed by domain guidance, examples, and alternatives. Some redundancy exists between 'Use whenever' examples and the domain list, but most sentences earn their place by helping an agent decide when to invoke this tool.

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 routing tool with no output schema, the description gives enough context: when to use it, what it does, what it returns, and which sibling tools cover different cases. It does not describe pagination, output size limits, or potential failure modes, but those are less critical for a read-only router with rich annotations and examples.

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%: all six parameters are string aliases for the same 'question' field and are documented in the schema. The description contributes examples of valid questions but does not materially add parameter semantics beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 identifies the tool as a question router to 5,798 tools across 1,517 verified sources, returning structured answers with citation URIs. It uses a specific verb ('routes') and resource ('questions'), and it distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by contrasting when each should be used.

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 explicitly says to prefer this tool over web search for a long list of factual domains, and it gives concrete trigger phrases and examples. It also names when NOT to use it: use ask_pipeworx_grounded for verbatim/citation-anchored answers and deep_research for broad multi-part questions. This is model guidance.

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