massive_run_pipeline

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

The description discloses the pipeline's behavioral steps (search, fetch, store, query, apply) and notes efficiency gains. Annotations indicate idempotency and non-destructiveness, and the description does not contradict them. The description adds useful context about the composite nature beyond what annotations provide.

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 two sentences with no extraneous information. Key benefits and features are front-loaded, making it easy for an agent to quickly understand the tool's value.

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 composite tool with no output schema, the description is somewhat brief. It covers the pipeline steps at a high level but could benefit from more detail on intermediate results or error handling. Given the rich schema and annotations, it is minimally adequate but not comprehensive.

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?

Input schema coverage is 100% with clear descriptions for all 6 parameters. The description adds marginal value by mentioning SQL filtering and Greeks/technicals, but the schema already covers these. No significant additional meaning is provided beyond 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's purpose: a composable pipeline that combines search, fetch, store, query, and apply steps into a single call. It explicitly distinguishes itself from siblings like massive_call_api by highlighting the multi-step nature and round-trip savings.

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 complex data workflows that would otherwise require multiple calls, but does not provide explicit guidance on when to use versus simpler alternatives like massive_call_api or massive_query_data. No exclusion criteria or when-not-to-use context is given.

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