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

With no annotations, the description carries the full burden. It discloses that the tool lists paginated history of transfers and contract calls, and requires a valid JWT. However, it doesn't mention if the operation is read-only or any side effects, though read-only is implied. It lacks details on pagination behavior like total count or error handling.

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 two sentences, front-loaded with the core purpose. Every word is meaningful—no fluff, no repetition. It efficiently conveys the tool's function and a key prerequisite.

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 lack of an output schema, the description hints at the content (action history, transfers, contract calls) and mentions pagination and authentication. It covers the essential context for usage. However, it could be more complete by describing the return format (e.g., list with pagination metadata) or potential errors.

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%, with all four parameters described in detail. The description adds context that the JWT comes from a specific authentication tool and that the list is paginated, but these are already clear from the schema. It does not significantly enhance understanding beyond what the schema provides.

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 lists paginated action history (transfers, contract calls) of an authenticated smart wallet. This is a specific verb-resource combination, and it distinguishes from siblings like fuse_send_erc20 or fuse_smart_transfer_token, which perform actions rather than list history.

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 indicates the JWT must come from `fuse_smart_wallet_authenticate`, providing a clear prerequisite. It also implies usage for retrieving history with pagination. However, it does not explicitly exclude when not to use or list alternatives like other tools that might return similar data.

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