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

Annotations are present (read-only, idempotent, non-destructive, closed-world), so the safety bar is lower. The description still adds substantial behavioral context: Bitcoin anchoring for immutability, late-landing sources, provisional partial days, the distinction between latest/latest_complete, and the fact that some sources serve score/bands only. These are real traits beyond the annotations.

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 very long and front-loads a list of concrete questions (pump.fun, Kalshi, Polymarket, Hugging Face, Chicago crime, x402) before stating what the tool actually does. Key routing details like 'Same data as GET /api/indices' and the latest/latest_complete distinction are buried, making it hard to scan. Many sentences are informative but the structure is not front-loaded.

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 zero parameters, no output schema, and rich annotations, the description is functionally complete in coverage of concepts, anchoring, and provisional-day behavior. But it is disorganized and omits a clear statement of return structure at a glance; an agent must read the entire paragraph to know the list returns all indexes with period/value/band.

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?

There are zero parameters, so the baseline is 4. The description explains the shape of the returned periods (period, value, band, p25/p75 for WAGE, partial_day flags), which is useful given no output schema, though it concerns output rather than parameters.

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 opens with a long list of example questions and only later explains that Tickerz reads each as a daily index against its own normal, on-chain in Bitcoin. The core purpose (list all Tickerz indexes) is buried and never stated as a clear verb+resource. A sibling get_index likely serves individual indexes, but the plural scope of list_indices is not stated until 'Same data as GET /api/indices' and even then only implicitly.

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 opening 'Use when...' plus examples implies usage, and the later note about latest_complete versus latest gives some selection guidance between periods. However, it never states when to use list_indices instead of get_index, methodology, or other siblings, and the example-driven framing substitutes for explicit when-to-use rules.

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