getBulkTransactions

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds the time-bucket interval context, but does not disclose response format, pagination, or any rate limiting. With annotations covering the read-only nature, the description adds modest value but remains thin on behavioral details.

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 a single, concise sentence that wastes no words and front-loads the core purpose. It is appropriately sized for the tool's simplicity.

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?

The tool has four required parameters, no output schema, and a read-only annotation. The description is minimal but covers the essential function. However, it omits the response format, authentication requirements, and any caveats about the 'bulk' nature of data, leaving some ambiguity for an agent deciding whether to invoke this tool.

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 50%, with walletAddress and timeBucket described in the schema. The description reinforces these by mentioning 'wallet address' and '15-minute time bucket interval,' adding clarity. However, it does not address authToken at all, and chainName's fixed value 'somnia' is only represented by a schema const, leaving two of four parameters with incomplete guidance.

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 clearly states the tool 'provides bulk transaction data for a wallet address in a 15-minute time bucket interval,' specifying both the resource (bulk transaction data) and the unique time-bucket granularity. This distinguishes it from sibling tools like getTransactionsForAddress or getRecentTransactions, which do not mention bulk data or a 15-minute interval.

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 implies the tool is for bulk transaction data aggregated into 15-minute buckets, but it does not explicitly state when to use it over alternatives or provide exclusions. No guidance is given about prerequisites or comparison with sibling tools, so usage context is only implied.

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