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 that the tool retrieves essential fund details, but it does not mention return format, pagination, or any special behavioral traits. It adds some context by listing example fields, but lacks depth about what 'comprehensive data' includes or how results are structured.

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 two concise, front-loaded sentences. The first sentence names the API and resource, and the second lists example fields. Every word earns its place with no redundancy or 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?

For a simple one-parameter tool without an output schema, the description provides a basic purpose and example fields, but it omits details about the return structure and does not explain how it relates to the many sibling fund tools. Given the absence of annotations and output schema, the description could be more complete but is not severely inadequate.

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 schema already provides a clear description for the single 'symbol' parameter with 100% coverage. The description mentions 'ticker symbol' but does not add format or validation details beyond the schema, so the baseline 3 applies as the schema does the heavy lifting.

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 accesses comprehensive data on ETFs and mutual funds, listing example fields like ticker symbol, fund name, expense ratio, and AUM. It is specific about the resource type, but it doesn't explicitly distinguish itself from sibling tools like getETFList or getMutualFundQuotes, so the purpose is clear but not uniquely differentiated.

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 provides no guidance on when to use this tool versus alternative fund-related tools. There is no mention of exclusions, prerequisites, or suggested use cases, leaving the agent to infer usage solely from the tool name and general description.

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