get_fund_data

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 the error condition (raises for stocks/crypto) and the type of data returned. While it doesn't mention rate limits or auth, those are not critical for this read-only data retrieval 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?

The description is about 80 words, front-loaded with a clear purpose statement, followed by symbol constraints and return content. Every sentence adds value with no redundant fluff.

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 the output schema exists, the description appropriately omits return format details. It covers the essential behavioral context (fund/ETF-only error behavior) and symbol resolution workflow, making it complete for an agent to select and invoke the tool.

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 both 'symbol' and 'limit' already described in the input schema. The description reinforces the symbol format rule but doesn't add new parameter-level information beyond the schema, so a baseline of 3 is appropriate.

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 'Get fund/ETF profile data for a Yahoo symbol' with a specific verb and resource. It further specifies the returned data (overview, weightings, top holdings), distinguishing it from other get_* siblings like get_quote or get_estimates.

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?

Explicitly states 'Fund/ETF-only; raises for stocks and crypto' and instructs to resolve non-Yahoo tickers via the 'search' tool first. This gives clear when-to-use and when-not-to-use guidance with a named alternative.

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