Indexer: Transfers from address (outgoing) (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 behavioral context: it tells that the tool accepts VNS names and token symbols, and supports pagination. This extra info about input flexibility and pagination goes beyond the schema and annotations. No contradictions.

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 well-structured with a front-loaded purpose statement, followed by parameter highlights and usage guidance. It is efficient, covering all necessary points without redundancy. Slightly verbose but not wasteful.

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 presence of an output schema (context signals indicate it exists), the description covers endpoint, parameter formats, usage guidance, and relationship to a sibling tool. It also mentions pagination. No gaps are apparent for the tool's complexity.

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 baseline is 3. The description adds value by explaining that 'address' accepts VNS names and 'tokenAddress' accepts token symbols, which are not mentioned in the schema descriptions. It also mentions pagination, tying together the page/size/cursor parameters.

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 it queries outgoing transfers from the VeWorld Indexer, specifies the endpoint, and identifies required/optional parameters. It also distinguishes from sibling tool getTransfersOfAccount by noting it is a directional filter, and advises preferring the sibling unless only outgoing transfers are needed.

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?

Provides explicit when-to-use ('outgoing transfers', 'payments from wallet') and when-not-to-use ('prefer getTransfersOfAccount unless specifically need only outgoing transfers'). This gives clear decision criteria for the agent.

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