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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose a key trait: output includes percentage of NAV. However, it does not mention the default/max limit (already in schema), whether the list is sorted, what happens for invalid scheme codes, or any pagination or error behavior. It adds some context beyond the schema but is thin.

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, front-loaded sentence that states the core purpose and a key output detail. There is no redundant or extraneous information, making it highly concise and easy to scan.

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 two-parameter read tool with no output schema, the description is mostly complete: it specifies the resource (fund) and the output (top holdings with percentage of NAV). It could be improved by explicitly stating the return list format or noting the limit parameter's effect, but overall it is sufficient for an agent to invoke the tool correctly.

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 description coverage is 100%, so the parameters are already well-documented in the schema. The description adds no additional meaning about the parameters, but the baseline of 3 applies since the schema does the heavy lifting. The schema's descriptions for scheme_code and limit are clear and sufficient.

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 action ('Get') and the resource ('top holdings for a fund'), and adds the specific output detail 'with percentage of NAV'. This distinguishes it from siblings like find_funds_holding (which likely looks up funds by security) and get_fund (which returns fund metadata).

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?

Usage is implied by the description: when you need a fund's top holdings, this is the tool. However, there is no explicit guidance on when not to use it or mention of alternatives such as get_fund or find_funds_holding. It lacks the explicit when/when-not comparisons seen in higher-scoring tools.

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