Bitcoin held by public companies

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

With no annotations, the description carries the full burden. It usefully discloses provenance (company-filed XBRL, not market data) and timing semantics ('as of the filing period'), signaling reporting lag. It says nothing about universe size, refresh cadence, or whether it is a snapshot vs historical series.

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 with no filler, and the provenance qualifier is the most useful piece of information placed inline. It is terse, though for a whole-dataset tool a little more specificity would not be waste.

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?

No annotations, no output schema, and no parameters means the description is the only contract, and it stops at naming measures. It does not indicate the shape of the result (per-company rows? single aggregate?), coverage, or time span, which an agent needs to use it confidently.

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?

Zero parameters, so the baseline is 4. The description compensates somewhat by enumerating the returned measures (coins, fair value, cost basis), which is the closest thing to a field contract in the absence of an output schema.

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 the specific resource (Bitcoin holdings of public companies) and even the provenance (their own XBRL filings), plus the fields exposed (coins, fair value, cost basis). It is distinguishable from crypto_market and company_financials, though it never names a sibling to sharpen the boundary.

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 when-to-use guidance, no prerequisites, and no alternative named. The only contextual hint is 'as of the filing period', which implies the data is periodic rather than real-time, but that is inference, not guidance.

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