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

With no annotations, the description must disclose behavioral traits. It mentions 'real-time quotes' and 'current prices, performance changes, and key data,' but fails to clarify that the tool likely returns a bulk list (no symbol parameter is present) and does not explain the effect of the 'short' parameter beyond the schema. The lack of any required parameters and the singular optional boolean suggest a list endpoint, but this is not stated.

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 sentences, front-loaded with the primary purpose, and contains no fluff or redundant information. Every word 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?

The tool has only one optional parameter, yet the description does not explain how to specify which mutual fund(s) to query. Given there is no output schema, the description should clarify whether this returns a list of all mutual fund quotes or requires external context. The phrase 'various mutual funds' is vague and incomplete for effective tool invocation.

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 input schema has one parameter, 'short', with a description ('Whether to use short format'), so schema coverage is 100%. The tool description adds no additional meaning about parameters, so the baseline score of 3 applies.

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's function: 'Access real-time quotes for mutual funds' with a specific verb and resource. It distinguishes from sibling tools like getQuote and getETFQuotes by explicitly focusing on mutual funds.

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 mutual fund quote retrieval but does not explicitly state when to use this tool over alternatives like getQuote or getBatchQuotes. There is no mention of exclusions or alternative tools, leaving the agent to infer from the resource type.

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