Bundle 1-20 cross-niche queries in one call. Saves 50-92% vs. per-API. Free preview accepts up to 5; paid via Stripe session_id or x402 X-Payment header.
| Name | Required | Description | Default |
|---|---|---|---|
| free | No | If true, return free 1-row preview (capped at 5 queries) | |
| queries | Yes | ||
| session_id | No | Optional Stripe checkout session_id for paid full results |
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 key behaviors: bundling limit (1-20), free preview cap (5), and payment requirements via Stripe session_id or x402 header. This adds significant behavioral context beyond the schema, though it omits error handling and result structure.
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 extremely concise, using two sentences to convey purpose, quantity limits, cost savings, and payment methods. Every phrase earns its place with no fluff or repetition.
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 tool with 3 params and no output schema, the description covers the core usage: how to bundle, payment, and limits. It does not describe the return format or error behavior, but given the complexity and the presence of the schema for limits, it is fairly complete. Slight gap for edge cases.
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 67% (free and session_id have descriptions). The description adds meaning to 'free' (preview up to 5) and 'session_id' (paid via Stripe), but does not clarify the 'queries' parameter's 'q' field or the structure of each query object, relying on the schema's type enum. Moderate value 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 it bundles 1-20 cross-niche queries into one call, using the specific verb 'Bundle' and clearly distinguishing from per-API calls (likely the sibling datafood_query). This provides a strong sense of the tool's role and 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?
It implies use for batching multiple queries to achieve cost savings, and explains free vs paid modes with payment methods. However, it does not explicitly state when not to use it (e.g., for a single query) or name alternative tools, but the 'vs. per-API' phrase gives clear context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: bundling multiple queries, Q&A on a portfolio, executing a single query, and opening a watchable session. There is no overlap or ambiguity.
All tools share the 'datafood_' prefix and use snake_case. However, 'portfolio_ask' is a verb-noun order that slightly deviates from the noun-like pattern of 'bundle', 'query', and 'watch_session'.
With 4 tools covering single queries, bundled queries, portfolio Q&A, and agent sessions, the count is well-scoped for the domain. No tool feels extraneous or missing.
The tools cover core operations (query, bundle, portfolio analysis, session management). Minor gaps exist, such as lacking tools for payment management or listing sessions, but these are not essential for basic usage.