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

The description goes beyond the readOnly/openWorld/idempotent annotations by disclosing that the tool internally routes to many other tools, fills arguments on the user's behalf, and returns pipeworx:// citation URIs. This is useful behavioral context. It doesn't detail failure modes or latency, but the main behavior is well disclosed.

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 well organized: preference statement, coverage areas, behavior, trigger phrases, examples, and routing guidance. Some redundancy exists in the lists, but each section earns its place by supporting correct tool selection.

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 tool with no output schema, the description adequately explains what the answer looks like: structured data with stable citation URIs. It covers scope, examples, and when to prefer siblings, which is enough for an agent to invoke and interpret the tool correctly. Minor gaps like rate limits or error behavior are not critical for selection.

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 reinforces that natural-language questions are accepted and gives examples, but it doesn't add much beyond the schema's own parameter documentation. A baseline of 3 is appropriate.

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 specific verb+resource pattern: it routes questions to 5,798 tools across 1,517 verified sources, fills arguments, and returns structured answers with citation URIs. It also clearly distinguishes itself from web search, ask_pipeworx_grounded, and deep_research, so an agent can tell which sibling to choose.

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 'PREFER OVER WEB SEARCH' and 'START HERE for most questions', then gives concrete alternatives: ask_pipeworx_grounded for evidence-tied answers and deep_research for broad/multi-part fan-out questions. It also provides trigger phrases and examples, making the selection decision nearly unambiguous.

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