get_mutual_funds

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

No annotations are present, so the description carries full behavioral disclosure burden. 'Fetch' implies a read-only operation, but no details are given about return format, error handling, rate limits, or authentication requirements. 'Connected brokers' hints at a prerequisite but does not explain behaviors.

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 a single sentence that is front-loaded and efficient. Every word earns its place, with no redundancy or irrelevant information.

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?

With no output schema and no annotations, the description fails to explain return values or usage nuances. It is minimally sufficient for a simple read operation but lacks completeness regarding response structure and operational 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 description does not mention the 'broker' parameter at all. While the schema's enum and default provide some clarity, schema description coverage is 0%, and the description adds no semantic value beyond what the schema already offers.

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 fetches mutual fund holdings, using a specific verb and resource. It distinguishes from sibling tools like get_holdings (general) and get_us_stocks/gold by specifying 'mutual 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?

No guidance is provided on when to use this tool versus alternatives like get_holdings. The phrase 'from connected brokers' implies a prerequisite but does not explain when this tool is preferred or what to do if brokers are not connected.

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