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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-obvious context: the data source (etf.com structured data via a residential proxy) and the billing model ($0.002 USDC per successful call via x402, failures not charged). It does not mention rate limits or failure modes beyond billing, so it stops short of a 5.

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?

Three sentences, front-loaded with what the tool returns, then provenance, then price. The field enumeration is slightly list-heavy and partly duplicates the output schema, but nothing is padding.

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?

An output schema exists, so return values need no further explanation; provenance and cost are disclosed, and the single required param is documented. The only real gap is selection guidance relative to the many overlapping fund/market-data siblings in this server.

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 a single parameter at 100% schema description coverage (ticker with SPY/QQQ/VTI examples), the schema already carries the semantics. The description only marginally adds by implying the symbol must be a US-listed ETF ticker, which is worth noting but is close to what the schema implies.

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 names the resource (ETF.com fund profile), the scope ('US-listed ETF'), and enumerates the fields returned (issuer, expense ratio, AUM, benchmark, etc.), so an agent knows exactly what it gets. It does not name a sibling or explain how it differs from finance_morningstar, finance_stockanalysis, or finance_yahoo_finance, which also serve fund/security data.

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 scope statement ('US-listed ETF') and the per-call price hint, but there is no explicit when-to-use/when-not guidance and no comparison to the many adjacent fund-data siblings. The agent must infer selection from the ETF-only scope rather than being routed.

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