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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal that the tool provides an overview with specific metrics and implies a read-only snapshot, but it does not mention data scope, freshness, rate limits, or response behavior beyond what the output schema already supplies.

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 compact line with no filler. The core purpose is front-loaded, the metric scope is parenthetically specified, and the parameter example earns its place by making the schema more actionable.

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 one-parameter tool with an output schema, the description provides sufficient context: the resource, the key metrics covered, and a realistic code example. It lacks explicit guidance on when to choose this tool over sibling tools, but that gap is already accounted for in usage_guidelines.

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?

With 0% schema description coverage, the description compensates by giving a concrete example, 'code=sh510300', which clarifies the expected string format for an exchange-prefixed ETF code. It does not exhaustively document valid formats, but for a single obvious parameter this example adds real value beyond the bare 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 identifies the resource (ETF) and the purpose (概览/overview), and specifies the included dimensions: 规模/溢折率/资金流. This distinguishes it from broader siblings like ashare_quote or ashare_fund, though the distinction is not stated explicitly.

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 explicit guidance is given about when to use this tool versus alternatives such as ashare_fund or ashare_quote. The only usage hint is the example 'code=sh510300', which demonstrates the parameter but does not explain selection criteria or exclusions.

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