get_etf_profile

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

Discloses that include_gettex uses a WebSocket and can block outside trading/network conditions. No annotations exist, so description carries full burden; lacks disclosure on authentication, rate limits, or read-only nature.

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 with clear front-loading of purpose, followed by contents and a behavioral note. No fluff, but could be slightly more structured.

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?

Description explains main purpose and includes list of output fields, but fails to describe expand_allocations and timeout_seconds. Given 0% schema coverage and 4 parameters, this is insufficient.

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 schema coverage at 0%, description adds meaning for isin (required) and include_gettex (explains blocking). But expand_allocations and timeout_seconds are not mentioned, leaving gaps.

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 returns comprehensive ETF profile data for one ISIN, listing included fields. It distinguishes from sibling tools like search_etfs and get_chart by focusing on a single ISIN's full profile.

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?

Implies usage when detailed ETF profile is needed, and warns against using include_gettex=true unnecessarily due to blocking. However, no explicit when-to-use vs alternatives or exclusions.

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