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

No annotations exist, so the description must carry the disclosure burden. It does reveal useful behavior: a no-argument call returns the list, and each ranking is based on a single stated figure. But it does not state whether the operation is read-only, what a response contains, or how invalid slugs or limits behave.

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?

Three sentences with concrete examples and the default-call behavior included. It is concise and front-loaded with the core resource; the first sentence is slightly awkward ('or one of them'), but there is no padding.

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?

With no output schema, annotations, or parameter documentation, the description leaves significant gaps: no accepted slug values, no limit semantics, and no indication of the response format. It is enough for a bare no-argument call but not for confident parameterized 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?

Schema coverage is 0%, so the description must explain 'slug' and 'limit'. It gestures at slug selection ('or one of them' / 'stated set') and says no-argument calls succeed, but it never names or describes the 'limit' parameter and provides no slug vocabulary.

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 identifies a specific resource ('ranked lists ETFIQ publishes') and clarifies that each list ranks one published figure with concrete examples. It doesn't explicitly contrast with sibling tools, but the resource is distinct enough that a caller can tell this from 'etf_holdings' or 'etf_screen'.

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 phrase 'Call with no argument for the list' gives a clear default invocation, and the examples imply this is for published ranked lists rather than screening or search tools. However, it never states when to choose this over siblings like 'etf_theme' or 'etfiq_list', nor when not to use it.

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