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

With no annotations, the description carries the full behavioral burden, and it does usefully disclose the default output shape and the rationale (avoid overwhelming agent context). It omits other operationally important traits for a 1,000-item batch call: partial-failure semantics, rate limits, timeouts, or cost. Partial but not complete disclosure.

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 with the core capability front-loaded and the parameter guidance following. The second sentence's rationale is slightly verbose but earns its place by explaining the default output behavior.

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?

There is no output schema, so the description should cover return shape, and it only partially does (summary vs full). Combined with zero schema coverage on the nested `items` structure, an agent lacks enough information to construct a correct request or interpret partial results.

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 0%, so the description must compensate. It explains detail_level's effect and default, but the required `items` parameter is an untyped object with additionalProperties:true and the description never says what fields a transaction item must contain, leaving the most important input dimension undocumented.

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 gives a specific verb (Check), a specific resource (crypto transactions), and a scope boundary (up to 1,000 in one request), which distinguishes it from the singular sibling check_transaction. It stops short of naming that sibling explicitly, so an agent must infer the batch-vs-single split.

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 clear conditional guidance for the detail_level parameter ('set full when individual results are needed'), which is real usage advice. However, it never says when to prefer this batch tool over the sibling check_transaction or preflight_transaction, nor does it state any prerequisites, so tool-level selection is left to inference.

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