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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely useful behavior beyond that — the capture is stateful and only retained for follow-ups for up to two hours, and cycle_id from this call is the token that unlocks them — but it says nothing about response size, pagination totals, or what expiry means for an in-flight session.

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?

Three tight sentences, front-loaded with the 'Start here' routing cue, then the paging recipe, then the retention caveat. Every sentence carries information, though 'captured operands' is opaque phrasing that costs clarity without adding precision.

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 seven parameters, no output schema, and rich annotations, the description covers the entry-point workflow and follow-up token lifecycle well. However, because no output schema exists, the description is the only source for what an 'overview' actually returns, and it never characterizes the response fields or size — a real gap for a tool meant to be called first.

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 100%, so every parameter is already documented, including the detail enum, domain requirement, and offset's dependency on cycle_id. The description only restates the common combination (detail=signals plus cycle_id) and adds no syntax, defaults, or interplay beyond the schema, so the baseline 3 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 resource (one BTC capture) and the shape of the result (a compact overview) and explicitly positions the tool as the entry point with 'Start here'. It is clear enough to act on, though the jargon 'capture' and 'synthesis' leaves some ambiguity about what is actually summarized, and the sibling get_daily_brief is never contrasted.

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 gives concrete usage direction: use it first, set detail to signals and pin cycle_id to page operands, and note that follow-ups are only possible within a two-hour retention window. There is no explicit when-not-to-use or a named alternative, which keeps it short of a 5.

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