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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context: it routes to 5,724 tools, fills arguments automatically, returns stable pipeworx:// citation URIs, and notes it works on every tier with one fast call. This gives the agent a realistic picture of what happens on invocation.

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 every section earns its place: preference statement, domain list, behavior, trigger phrases, examples, default status, and escalations. It is front-loaded with the most critical instruction ('PREFER OVER WEB SEARCH') and structured logically. Slightly verbose, but the complexity of a default entry point to 5,724 tools justifies the length.

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?

Despite having no output schema, the description covers the return format ('structured answer with stable pipeworx:// citation URIs') and situates the tool among alternatives. It explains what domains it covers and how to escalate to grounded research or deep_research. Minor gaps exist (e.g., no mention of ask_pipeworx_beta or failure behavior), but for an open-world read-only query tool this is largely complete.

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 coverage is 100%, and the schema already describes the lone meaningful parameter (question) as a natural-language request accepting several aliases. The tool description adds example questions and domain guidance, but this is more about usage than new parameter semantics. Baseline 3 is appropriate since the schema carries the load.

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 the tool's function: it answers factual questions by routing to 5,724 tools across verified sources and returns structured answers with citation URIs. It also explicitly distinguishes itself from siblings like ask_pipeworx_grounded and deep_research, so an agent can tell them apart without inspecting schemas.

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 provides explicit when-to-use guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and gives specific trigger phrases and examples. It also names alternatives and the conditions for stepping up ('for a hallucination-resistant single answer... use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research'), leaving no ambiguity.

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