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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully reinforces the closed-world trait by promising the 'whole published set rather than a sample', but it says nothing about pagination, result size caps, or behavior for an unrecognized theme.

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 tight sentences with the resource and ordering front-loaded before the use-case sentence. The 'Scout and Strategist:' persona prefix is minor noise that adds no operational value but costs little.

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 two-parameter read tool with no output schema, the description covers what comes back and in what order, which is most of the burden. It still omits theme string format, the role of limit, and empty-result behavior, leaving gaps an agent would hit on first use.

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%, the description should carry parameter meaning, and it only implies 'theme' through phrasing. Worse, 'returns the whole published set rather than a sample' sits in tension with the undocumented 'limit' parameter, leaving the agent unsure whether limit truncates the set or is ignored.

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 a specific resource (every US-listed fund in a theme), the ordering (largest first), and the payload (fees charged, share already in the S&P 500), so an agent knows exactly what it gets back. It does not distinguish itself from the near-identical sibling 'etf_themes', which an agent could easily confuse with this tool.

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 concrete triggering questions ("what X ETFs are there", "top X ETFs"), which is clear when-to-use guidance. It stops short of naming alternatives such as etf_screen or etf_search, or stating when a filtered screen is preferable to enumerating the whole theme.

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