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

With no annotations, the description carries the burden of behavioral disclosure. It transparently describes output composition, ordering, and the complete-set behavior. However, it does not disclose how the optional limit parameter affects results or what happens for unknown themes.

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 two sentences and front-loads the core output and ordering. The all-caps 'USE THIS' is slightly noisy but efficiently adds usage routing.

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 list-style tool, it covers scope, ordering, and key output metrics. However, with no output schema and no annotations, the optional limit behavior and theme value semantics remain underspecified, which an agent needs to call it reliably.

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?

Schema description coverage is 0%, so the description must compensate for both parameters. It implies the meaning of 'theme' through 'in a theme', but the 'limit' parameter is completely unexplained, and no format or accepted values for theme are provided.

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 exactly what the tool returns: every US-listed fund in a theme, sorted largest first, with expense information and S&P 500 overlap. It distinguishes itself by emphasizing 'the whole published set rather than a sample', though it does not name sibling tools 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?

It gives an explicit instruction to use this tool for 'what X ETFs are there' or 'top X ETFs' questions, and clarifies that it returns the complete set rather than a sample. It lacks when-not-to-use guidance or named alternatives, which prevents a perfect score.

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