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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description adds valuable operational context: API key requirement, a 200-column response cap with series_next_offset pagination, and the effect of related=True. It still leaves the meaning of `lane` values and the clock behavior somewhat vague.

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?

Dense but front-loaded: the core operation comes first, followed by layer, related, period, pagination, and auth. Some phrasing is cryptic ('on one clock', backticked identifiers) but no sentence is obviously wasteful.

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 six-parameter, no-output-schema read tool, the description covers the important call-shaping details: id source, layers, periods, related expansion, pagination cap, and API key. Missing lane enumeration and limit meaning keep it from being fully complete.

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 carry parameter meaning. It explains market, layer values, period values, and related well, but leaves `lane` values (only the default 1min appears in schema) and `limit` semantics undefined, so compensation is partial.

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?

States a specific verb and resource: fetch one whole market's every series in a single call, and names the id source (tilla_markets) with examples. This clearly distinguishes it from list-oriented siblings like tilla_markets and point-query siblings like tilla_tick.

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?

Establishes clear context: use this when you want the complete set of series for one market across layers and periods, with related=True for connected markets. It does not explicitly state when to prefer siblings such as tilla_window or tilla_latest, so exclusions and alternatives are only implied.

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