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

Annotations already establish read-only, open-world, and idempotent behavior. The description adds useful context beyond those annotations: it routes to sub-tools, fills arguments, returns stable pipeworx:// citation URIs, and is described as one fast network call. No contradiction exists with annotations.

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 longer than average but front-loads the most important behavioral guidance, provides a useful domain list, and includes concrete examples. Almost every sentence contributes to usage decisions, though the repeated 'default entry point' and 'START HERE' phrasing is slightly redundant.

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 routing tool with no output schema, the description explains what the tool returns, when to use it, and what kinds of questions it handles. It is complete enough for an agent to select and invoke it confidently, though it does not describe failure modes, rate limits, or when to prefer a sibling tool.

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?

The input schema already documents all six parameters as aliases for the single `question` parameter, with 100% schema coverage. The description adds example queries and emphasizes natural-language questions, but it does not meaningfully extend the semantic meaning already present in the schema.

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 routes natural-language questions to the appropriate data source among thousands of verified tools and returns structured answers with citation URIs. It distinguishes itself from web search and gives concrete examples, so an agent can understand exactly what ask_pipeworx does.

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 gives explicit when-to-use guidance: prefer it over web search for factual, authoritative, real-world data, and use it even when web search could answer the question. It also positions it as the default entry point, but it does not explicitly describe when to choose sibling tools like ask_pipeworx_grounded or deep_research instead.

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