search_funds

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

No annotations exist, so the description must bear full behavioral transparency. It discloses the tool's read-only search nature and return type, but lacks details on matching behavior (e.g., partial, fuzzy), pagination, result limits, or performance. It is adequate but minimal.

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 concise sentences front-load the purpose and return value. No unnecessary words. Every sentence adds 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 simple search tool with one parameter and no output schema, the description adequately states purpose, input, and output (scheme codes and names). It could mention result count or behavior for invalid input, but is not incomplete.

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 100% with examples in the parameter description. The tool description adds a set of concrete examples ('HDFC Top', 'SBI Small Cap', etc.), providing additional clarity beyond the schema alone.

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 searches 'Indian mutual funds by name' and returns 'scheme codes and names', distinguishing it from siblings like search_symbol (stocks) and get_fund_details (specific fund). The verb 'Search' and resource are explicit.

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 finding fund codes, but does not give explicit when-to-use or when-not-to-use instructions relative to siblings like search_symbol or get_fund_details. No alternatives are mentioned.

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