Indexer: Transactions by origin or delegator (v1)

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the tool returns decoded events and fetches from an external indexer with optional filters and pagination, providing behavioral context beyond what annotations offer.

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 one sentence that efficiently conveys the tool's purpose, source, required inputs, optional inputs, and return type. Every word adds value, and it is well front-loaded.

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 tool's complexity (9 optional parameters, output schema provided), the description is complete enough. It covers the main input categories and return type. It could mention mutual exclusivity of origin and delegator, but overall it suffices.

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 coverage is 100%, so the description's mention of 'origin or delegator address with optional time filters and pagination' does not add significant meaning beyond the schema. It summarizes but does not elaborate on parameter interactions or constraints.

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 action (query), the resource (VeWorld Indexer /api/v1/transactions), and key parameters (origin/delegator, time filters, pagination). It distinguishes from siblings like getDelegatedTransactions and getContractTransactions by focusing on origin or delegator address and noting return of decoded events.

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 usage when querying by origin or delegator address but does not explicitly differentiate from siblings like getDelegatedTransactions or getContractTransactions. No when-not-to-use or exclusion criteria are provided.

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