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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered without description text. The description adds the useful behavioral detail that each theme comes back with a fund count, but says nothing about ordering, size, or whether the list is exhaustive/paginated.

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 with zero filler, and the payload description is front-loaded before the usage instruction. The 'Strategist:' prefix is minor noise that adds no meaning for an agent.

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 zero-parameter lookup with no output schema, the description covers what comes back (theme names plus fund counts) and what to call next. Only the return shape and any result-size behavior are left implicit, which is a small gap at this complexity.

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 takes no parameters and the schema is an empty object at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level explanation is needed or missing.

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 states concretely that the tool returns every theme ETFIQ publishes plus a fund count per theme, which is more specific than the title 'All themes'. It implicitly distinguishes itself from the sibling etf_theme by positioning this as the enumeration step, though it never names the contrast 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?

'Call when unsure what a theme is called, then etf_theme' gives a clear trigger condition and an explicit follow-up call in the sibling tool. It stops short of stating when not to use it (e.g., if you already know the theme name, skip straight to etf_theme).

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