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

Annotations already mark readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds behavioral context: it routes to one of 6,053 tools, returns structured answers with pipeworx:// citation URIs, works on every tier, and is a single fast call. This is useful beyond annotations and aligns perfectly with 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 long but every sentence earns its place: preference, scope, examples, comparison to siblings, and step-up guidance are all front-loaded and organized. It's dense yet efficient, with no filler. The complexity of the tool (6k sources) 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?

Given the high complexity, full schema coverage, no output schema, and informative annotations, the description is complete. It covers what the tool does, when to use it, how it behaves (citations, speed), and how it differs from siblings. An agent has everything needed to call 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 coverage is 100% with a clear description of the 'question' parameter and its aliases. The description doesn't add extra parameter semantics, but it does provide illustrative examples of questions, which is more usage guidance than parameter meaning. Baseline 3 is appropriate given the schema fully documents the parameter.

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 factual questions to authoritative structured data sources and returns cited answers. It enumerates specific domains (SEC, FDA, FRED, etc.), gives concrete examples, and distinguishes it from siblings like ask_pipeworx_grounded and deep_research. This is a precise verb+resource with scope.

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 instructs to prefer this tool over web search, labels it as the default entry point, and provides step-up conditions for ask_pipeworx_grounded (hallucination-resistant answers) and deep_research (broad/multi-part questions). Also notes it handles breaking news via live feeds. Clear when-to-use and when-not-to-use with alternatives.

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