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

With no annotations available, the description must carry the behavioral burden on its own. It does so by stating the full result set — every published theme and the count of funds in each — which implies a read-only enumeration. It does not specify response ordering or structure, but the no-parameter signature and simple list behavior make that a minor gap.

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?

Two short sentences, both substantive: the first states the resource and output, the second states when to call it and what to use next. No filler or repeated schema content.

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 parameterless tool with no output schema, the description gives everything needed to select and invoke it correctly: what it lists, what counts are included, and how it fits into the workflow with `etf_theme`. An agent can confidently call it without further 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 tool has zero parameters, so schema coverage is trivially 100% and there is nothing for the description to add about argument meaning. The baseline for a parameterless tool is 4, and the description does not need to compensate for any schema gap.

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 tool as a catalog of every theme ETFIQ publishes, with one concrete output: how many funds each holds. This distinguishes it from the sibling `etf_theme`, which is the follow-up lookup, and from `etf_search` and `etf_rankings`.

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?

It gives an explicit trigger: 'Call when unsure what a theme is called', and names the next tool to use, `etf_theme`. This is direct when-to-use guidance and a clear pointer to the alternative, leaving no ambiguity about when this tool is appropriate.

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