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

Annotations already mark the tool read-only/idempotent, but the description adds real behavioral context: it routes internally to over 5,000 tools, 'fills arguments', returns stable 'pipeworx://' citation URIs, 'works on every tier' and is 'one fast call'. This goes beyond what annotations convey and does not contradict them.

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 dense and front-loaded with the key directive, but it is long, with repeated emphasis ('START HERE', 'default entry point', 'works on every tier'). All sections are useful, but it could be tightened by trimming redundancy.

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's broad scope and lack of an output schema, the description covers selection criteria, trigger phrases, examples, internal behavior, alternatives, and return format ('structured answer with stable pipeworx:// citation URIs'). An agent has enough information to select and 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 the description restates that the input is a natural-language question via examples. However, it adds no parameter nuance beyond the schema's own alias list; the baseline of 3 applies 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 opens with 'PREFER OVER WEB SEARCH' and states the tool 'Routes the question to the right one of 5,724 tools across 1497 verified sources' and returns structured answers with citations. It names sibling alternatives (ask_pipeworx_grounded, deep_research) and clearly distinguishes itself as the default entry point, so an agent can tell it apart without opening 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?

It gives an explicit when-to-use rule ('START HERE for most questions'), lists trigger phrasing such as 'what is', 'look up', 'get the latest', and explicitly states when to step up to alternatives: 'Step up only when needed: for a hallucination-resistant single answer... use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research'. This is rich routing guidance.

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