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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context about what each ranking contains — that it ranks a single published number within a stated set — which is behavioral information not in the annotations. It does not say what happens with an unknown slug, or whether rankings change over time.

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 no padding, but the lead is a vague role metaphor rather than the key fact, so the useful information (what the rankings are, and the no-argument behavior) is not front-loaded. The concrete ranking examples earn their place; the 'Strategist and Scout' framing does not.

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, two undocumented parameters and no annotations gaps to lean on, the description should explain the shape of a returned ranking and the valid slug space. It gestures at the content of a ranking but leaves the agent unable to construct a valid slug or understand what 'limit' bounds.

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 carries the full burden. It partially compensates for 'slug' by implying that supplying one selects a single ranking, but it never says what slug values exist or how to obtain them, and 'limit' is not mentioned at all. Half the parameters remain unexplained in both schema and description.

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 conveys that this returns ETFIQ's published ranked lists, or one of them, and gives concrete examples of what a ranking measures (cheapest funds in a theme, leveraged funds furthest from their multiple, buffer funds closest to their cap). But the opening framing ('Strategist and Scout') is evocative rather than specific, and the dual mode (catalog of rankings vs. a single ranking) is implied rather than stated with a clear verb+resource. Siblings like etfiq_list, etfiq_sections and etf_screen are not distinguished.

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 with no argument for the list' is a real usage instruction that tells the agent how to get the catalog versus a single ranking. Beyond that there is no guidance on when to prefer this over etf_screen, etf_movers, or etfiq_list, and no exclusions or prerequisites. Usage is implied but not routed.

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