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

No annotations, so the description carries the full burden and does disclose real return-shape behavior: a SLIM game tag {status, target_id, zt_regime, provenance} instead of the full block, ascending order by bar_ts, and that absent bars are honest gaps with no filling. It omits auth, rate limits, and pagination behavior, but the core behavioral traits are 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?

Information-dense and front-loaded with the core purpose, but delivered as one run-on sentence with heavy nested parentheticals that make it hard to scan. Every clause is relevant, yet the structure hurts readability.

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 and no annotations, the description steps in to describe the return shape, ordering, and gap behavior, which is what an agent most needs. It leaves out pagination/limit behavior and the meaning of fields like zt_regime/provenance, so it is strong but not 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 only 50% and the description adds little parameter-level meaning: it does not explain `limit`, the `timeframe` enum choices, or how `since` interacts with pagination. `symbol` and `since` are already documented in the schema, and the bar_ts/ordering remarks are return-format notes rather than parameter semantics.

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+resource and scope: 'per-bar state timeline for a symbol/timeframe'. It explicitly distinguishes itself from decker.get_market_state (structured CR1) and its persisted event list, so an agent can separate this tool from its closest sibling without opening either schema.

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?

It names alternatives and the condition that routes to them ('NOT the structured CR1 of decker.get_market_state; for the persisted event list use decker.get_market_state events'). It also implies the use case (read status transitions across bars). It does not spell out a crisp when-to-pick-this-tool-vs-siblings rule, keeping it below a 5.

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