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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so safety is covered. The description adds real behavioral context the annotations do not: output is tiered, with the base response covering BTC and the exit_desk_full tier adding ETH and venue-failure data. That is valuable, but it is delivered as a cryptic fragment with no explanation of what happens to a non-subscriber call.

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?

Two short fragments with no filler, and the metric list is front-loaded. However, telegraphic phrasing like 'effective/top venue' and 'Subscriber exit_desk_full' is compressed past the point of clarity rather than earning its brevity.

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, the description carries the burden of explaining return values, and it only lists metric names without format, time window, or ordering. The tier-gating note is a useful addition, but an agent still cannot predict the response shape or confirm whether 'today' (from the title) fixes the lookback window.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 names the metrics returned (HHI, effective/top venue, venue depth) and the asset scope (BTC two-sided depth), which tells an agent roughly what the tool computes. But there is no verb and no differentiation from siblings like liquidity_tiers, depth_episodes, or unwind_watch, so the agent must infer that this is a concentration-measurement read rather than tier classification or episode detection.

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?

There is no statement of when to call this tool, when not to, or which sibling to prefer for related questions. The 'Subscriber exit_desk_full' fragment hints at a tier gate but does not tell the agent how to proceed if it lacks that tier.

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