ae_pipeline_rag

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

No annotations are provided, so the description carries the full burden. It discloses the multi-step nature (fetch→extract→chunk→retrieve→summarize) and the truncation-prevention behavior, but omits whether calls are read-only, latency/cost implications of a chained pipeline, external API dependencies (RxNav), or failure modes. Significant gaps for an unannotated multi-stage tool.

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?

Two sentences, front-loaded with the tool's identity and scope, then the operational rationale. Zero waste and efficiently sized for the tool's complexity.

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 5-param, nested-schema, no-output-schema, no-annotation pipeline tool, the description covers purpose and motivation but is thin on behavioral details: no return shape, no error handling, no resource/latency expectations. The schema covers parameters, but the behavioral gap leaves an agent with unanswered operational questions.

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%, so the schema already documents all five parameters with examples and ranges; baseline would be 3. The description adds pipeline-level context about how parameters feed the fetch/retrieve stages, marginally exceeding the baseline.

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?

States a specific verb chain (fetches, extracts, chunks, retrieves, summarizes) and a specific resource (RxNav drug terminology data) with a stated rationale (prevent LLM response truncation). It distinguishes itself from siblings by being a multi-step pipeline rather than a single lookup, though it doesn't explicitly name the siblings it supersedes.

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 implies usage for comprehensive drug terminology analysis and explains the truncation-avoidance rationale, but offers no explicit when-to-use vs. when-to-call a sibling like search_drug_by_name. No exclusions or routing guidance are given.

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