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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the bar is lower. The description still adds real behavioral context: the print is 'delayed', terms are 'cited' with filing and as-of dates, and missing windows 'come back as named gaps' rather than silent nulls — genuinely useful for an agent interpreting results.

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?

A single front-loaded sentence that leads with the core action before the field enumeration. It is dense and listy, but because no output schema exists the enumeration is load-bearing rather than filler.

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 correctly carries the burden of describing return fields and even flags the data-quality behavior for missing windows. Combined with schema-documented input and annotation-covered safety, an agent has enough to call it correctly; only explicit usage routing to siblings is absent.

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?

One parameter with 100% schema description coverage, and the schema already supplies example tickers (STRF, STRC, etc.) plus length bounds. The description only restates 'by ticker' and adds no format or validation detail beyond the schema, so 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?

States a specific action (retrieve one bitcoin-treasury preferred) scoped to a single ticker, which implicitly contrasts with the plural/aggregate siblings like get_treasuries and get_yield_leaderboard. The resource is unambiguous, though no sibling is named explicitly.

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 description enumerates what comes back but never states when to use this tool versus alternatives such as get_treasuries (full list) or get_yield_leaderboard. 'By ticker' hints at a single-entity lookup, but there is no explicit when/when-not guidance or exclusion criteria.

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