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

With no annotations provided, the description carries the full burden of transparency. It discloses that the tool returns the percentage of assets allocated to regions, which suggests a read-only operation, but it does not describe the response structure, whether data is historical or current, or any limitations.

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 only two sentences, but it contains promotional fluff ('Gain insight', 'helping you make informed investment decisions') and redundancy ('This tool provides detailed information' echoes the first sentence). It could be more concise without losing substance.

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 with no output schema, the description provides a reasonable overview of what is returned (percentages by region). However, it does not specify the return format (list vs. single object), naming conventions for countries, or whether the tool expects an ETF symbol versus a mutual fund symbol.

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 already describes the single 'symbol' parameter as 'Fund symbol' with 100% coverage. The description adds context that the tool applies to ETFs and mutual funds, but it does not provide examples, format requirements, or additional meaning beyond the schema.

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 that the tool provides percentage asset allocation by country for ETFs and mutual funds, which differentiates it from related tools like getFundSectorWeighting. However, it uses vague verbs like 'Gain insight' instead of a direct action verb such as 'Returns' or 'Gets'.

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 it should be used when needing country-level allocation data for funds, but it does not explicitly state when to use it versus alternatives, nor does it mention exclusions or prerequisites. The context is clear but lacks explicit guidance.

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