Classify transaction batch

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

The description goes well beyond the readOnly/idempotent/openWorld annotations by detailing the per-transaction result structure, the handling of complex multi-step transactions, supported chains, and the effect of firm policy parameters. It does not discuss rate limits or authentication requirements, but those concerns are less critical given the annotations already establish a safe read-only and idempotent operation.

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?

The description is information-dense without being padded: it covers scope, output fields, special handling for complex transactions, supported chains, and policy parameters in a well-organized flow. The core action and key constraints are front-loaded, and every sentence adds value.

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?

Given the complexity of the tool, the rich output schema, and the annotations, the description is complete enough for an agent to select and invoke it correctly. It explains return values, constraints, special-case behavior, supported networks, and optional policy-driven parameters without leaving critical operational gaps.

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 the schema already fully documents transactions, firm_id, and engagement_id. The description reinforces the firm_id/engagement_id policy behavior and mentions the max batch size, but it does not add substantial meaning beyond the structured schema descriptions. Baseline 3 is appropriate.

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 opens with a precise verb and resource: 'Classify a batch of blockchain transactions (up to 100)'. It clearly distinguishes itself from classify_transaction by emphasizing batch processing, and enumerates the concrete output fields an agent can expect. The purpose is immediately identifiable and not a tautology of the tool name.

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 clearly states the intended use case: accounting platforms integrating CTE as their classification layer, with batches up to 100 transactions. It gives useful context about when to use this batch tool, but it does not explicitly mention when to prefer classify_transaction or other sibling tools, so it stops short of a full when/when-not comparison.

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