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

No annotations are provided, so the description carries the burden. It discloses that limit=0 returns all ~13k names, that results are ranked/sorted, that each item includes both absolute suggested_position_pct and relative normalized_weight, and that normalized_weight sums to ~100% across the returned set. It clearly indicates the output structure and how to interpret weights, which is critical for the user. It does not discuss rate limits or performance degradation for large universes, but the core behavioral contract is well covered.

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 three sentences, dense with useful information, and front-loaded with the core purpose. Every sentence adds value: the first states what it returns, the second gives the two usage modes, the third tells the user which output field to use. No fluff or repetition of the tool name.

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?

Given the schema has no parameter descriptions, no annotations, and no output schema, the description is remarkably complete: it covers the two main use cases, the meaning of limit=0, the returned fields (absolute and relative weights), how to interpret normalized_weight, and the relationship between parameters and mode. The tool is more complex than typical list tools because it supports both screening and basket sizing, but the description covers both paths adequately. Minor gaps (e.g., max_weight semantics, sort direction) are acceptable given the constraints.

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% and nothing is documented in the schema, so the description must compensate. It explicitly explains limit (0 = all ~13k names, meaning all), tickers (basket path), and implicitly explains min_decile and side via the screening/ranking mode. It also explains the meaning/purpose of normalized_weight as a rebalance target summing to ~100%. It does not explain max_weight, normalize, or min_decile in detail, but the major semantic gaps are filled.

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 uses a strong verb phrase ('return the ENTIRE scored universe'), specifies the resource (scored universe ~13k names), and distinguishes two distinct modes: with tickers (sizing a basket) vs without (screening/ranking). It also names sibling-like concepts (per-holding rebalance path vs screen/rank) which helps differentiate it from related tools.

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 description explicitly states when to use each mode: 'Pass tickers=AAPL,NVDA,… to score+SIZE a specific holdings basket (the per-holding rebalance path); omit it to screen/rank the universe (limit/min_decile/side).' It also explains the meaning of limit=0 (all ~13k names), giving concrete usage context and implicating the relevant parameters.

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