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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses specific behaviors: returns top constituents by weight, includes FRED spot and proxy prices for a specific list of commodity ETFs, and provides tool recommendations. It does not mention limitations, error handling, or response format, but the described behavior is quite detailed for a rollup tool.

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 front-loaded with a concise summary phrase ('One-call ETF intelligence rollup') and then expands with necessary detail. The second sentence is long with a ticker list, but every part serves a purpose (explaining commodity handling and usage admonition). It is not overly verbose for the richness of information conveyed.

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?

In the absence of an output schema, the description outlines the main return components: top holdings, commodity spot/proxy prices, and tool recommendations. It also provides contextual guidance for when to use it. It could be more complete by addressing non-commodity ETF behavior explicitly, but the implications are clear from the context.

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 schema only says 'Path parameter ticker (required)' which is tautological. The description adds meaningful semantics by indicating the ticker should be an ETF and listing specific commodity ETF tickers that trigger additional data (FRED spot, proxy price). This goes beyond the schema's empty description, though it could be more explicit about expected input format.

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's purpose: a one-call ETF intelligence rollup providing top holdings, commodity exposure, and tool recommendations. It uses a specific verb 'returns' and distinguishes from sibling tools like tengu_v3_intel_etf_holdings and tengu_v3_intel_commodities by emphasizing the rollup nature and the 'which other v3 tools work' feature.

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 explicitly instructs to call this tool before saying 'no data' on any ETF question, providing a clear when-to-use directive. It also contrasts with tools that lack coverage (analyst targets/insider flow), implying when alternatives may not be appropriate. This gives strong usage guidance beyond just stating what it does.

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