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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true. The description adds useful behavioral context: it routes across thousands of tools, fills arguments automatically, and returns citations. It does not describe response format details or limits, but the safety profile is covered by annotations and 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 long but information-dense, front-loaded with the most important preference over web search. The 'actually, ask_pipeworx is the fastest single answer' aside after listing alternatives is slightly disorganized, but every sentence contributes actionable guidance.

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 complex router with no output schema, the description covers purpose, use triggers, examples, routing behavior, and sibling alternatives. It could add explicit response format or limitations, but no critical decision-making information is missing for an agent to select and 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?

Schema description coverage is 100% with every parameter documented as an alias for 'question'. The description adds no parameter-level detail beyond examples, so the baseline of 3 applies.

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 specific verb and resource: it routes a question to the right one of 5,767 tools across 1,506 verified sources, fills arguments, and returns a structured answer with stable pipeworx:// citation URIs. It clearly distinguishes itself from siblings by naming deep_research, ask_pipeworx_grounded, and search_within with their respective roles.

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?

Explicitly says 'PREFER OVER WEB SEARCH' and 'START HERE for most questions,' lists trigger phrases like 'what is', 'look up', 'find', and gives concrete example queries. It also provides condition-specific alternatives: deep_research for multi-source synthesis, ask_pipeworx_grounded for verbatim quotes, and search_within for explicit source/date range selection.

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