compare_mutual_funds

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

No annotations provided. Description only states 'compare 2-4 funds side by side' without disclosing what data is compared, output format, or any side effects. This lacks transparency for a comparison tool.

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?

One sentence, 8 words, front-loaded with key action. Efficient but could include more detail without harming conciseness, such as what aspects are compared.

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?

No output schema, no annotations, and minimal description. For a comparison tool, missing details on what data is compared (e.g., returns, NAV) and output format. Incomplete for effective selection.

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?

Single parameter 'scheme_codes' has no description in schema (0% coverage). Description does not explain what scheme codes are or how they map to funds. No value added beyond 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?

Description clearly states verb 'compare', resource 'mutual funds', and scope '2-4 funds side by side'. This distinguishes it from siblings like 'analyze_mutual_fund' which likely analyzes a single fund.

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?

Implicitly indicates use for comparing multiple funds, but no explicit when-not or alternatives. Siblings exist for single-fund analysis or specific data, but not mentioned.

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