amfi_fund_flows

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that AUM is approximate and that the tool links to a detailed data portal, which is useful context. However, it does not mention data freshness, update frequency, rate limits, or whether results are cached, which are important behavioral traits for a data retrieval tool in this domain.

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 moderately concise and well-structured: it opens with a clear summary, then provides a bulleted list of data types, and closes with an example call. The note about Morningstar Direct's cost is slightly tangential but adds persuasive context about the tool's value proposition, so it earns its place. The overall length is appropriate for a no-parameter tool.

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 that the tool has no parameters and an output schema (though not shown here), the description is quite complete. It lists all the key data types returned, includes a usage example, and establishes the source (AMFI). The only minor gap is not describing the exact output structure, but the output schema already handles that. For a simple tool, this description provides sufficient context.

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?

The tool has zero parameters, so the parameter semantics dimension benefits from the baseline of 4. The description provides ample context about the output (AUM, SIP flows, scheme counts) without needing to explain any inputs. There is no parameter schema to complement, so the description's clarity about what data is returned is sufficient.

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 provides AMFI mutual fund industry data including total AUM, SIP flows, scheme count by category. It uses specific verbs and lists concrete deliverables (Total AUM, SIP inflows, folios, scheme breakdown), making its purpose unmistakable. It also distinguishes itself from sibling tools like mutual_fund_nav by focusing on industry-level flows rather than individual fund NAVs.

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 when this tool should be used by noting that AMFI publishes data free compared to costly Morningstar Direct, and it lists the data types available. However, it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or alternative tool references. The context is helpful but not prescriptive.

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