nlm_research_pipeline

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

With no annotations, the description must disclose behavioral traits but fails to mention side effects, permissions, or atomicity. The tool creates resources and processes data, but the description does not warn about potential costs, limits, or the scope of the pipeline.

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 a single sentence, but it is under-specified for the tool's complexity. It lacks structure and omits important details, making it ineffective despite being brief.

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 complexity (4 parameters, many siblings, no annotations), the description is incomplete. It does not explain the pipeline's steps, the relationship between inputs and outputs, or what the returned artifact represents, even though an output schema exists.

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 0% and the description adds no parameter details. It does not explain what 'sources' (URLs?), 'questions' (text?), or 'output_format' (article/thread/report) mean, leaving the agent without semantic guidance beyond the schema types.

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 lists actions ('Create a notebook, ingest URLs, ask questions, and assemble content') but does not specify the primary purpose or how it differs from sibling tools like nlm_create_notebook or nlm_research. The verb-resource combination is unclear and lacks distinction.

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?

No guidance on when to use this tool vs alternatives such as separate calls to nlm_create_notebook, nlm_add_source, nlm_ask, and nlm_generate. The description does not provide context for appropriate usage scenarios.

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